Closed (fixed)
Project:
Drupal Commons
Version:
7.x-3.x-dev
Component:
Theme
Priority:
Major
Category:
Bug report
Assigned:
Reporter:
Created:
13 Nov 2012 at 00:22 UTC
Updated:
9 Jul 2013 at 13:42 UTC
Jump to comment: Most recent file
This may be an issue to the timeago module, but im not sure.
Use timeago for comment creation/changed dates enabled on admin/config/user-interface/timeago, default install, adding a comment to the event shows up like this:
<time datetime="2012-11-13T00:09:04Z" pubdate="pubdate"><span class="date-time permalink"><a href="/comment/1#comment-1" rel="bookmark"><span class="timeago" title="2012-11-13T00:09:04+00:00">Tue, 11/13/2012 - 00:09</span></a></span></time>
The inner span will be shown as link, since the anchor is around it. Disabling the setting turns it into this:
<time datetime="2012-11-13T00:09:04Z" pubdate="pubdate"><span class="date-time permalink"><a href="/comment/1#comment-1" rel="bookmark">Tue, 11/13/2012 - 00:09</a></span></time>
I havent found any preprocess in the theme, so I guess this is timeagos fault?
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | commons-timeago-displays-html-1838928-13.patch | 643 bytes | devin carlson |
| #4 | commons-timeago-displays-html-1838928.patch | 841 bytes | prashantgoel |
Comments
Comment #1
ezra-g commentedThanks.
Ultimately this is a themeing issue, but having Timeago formatting on these links wasn't intentional, so I've disabled them:
http://drupalcode.org/project/commons_activity_streams.git/commit/51c0892
Comment #2
ezra-g commentedComment #3
ezra-g commentedComment #4
prashantgoel commentedSubmitting the patch for resolving this issue.
Comment #5
matt v. commentedThe patch in #4 worked for me.
Comment #6
ezra-g commentedThis is a patch to AdaptiveTheme's at_core project. Should it be a patch against Commons Origins?
Comment #7
WebSinPat commentedHello, I'm having the same issue in commons 7.x.3.2
I'm just wondering what is the correct fix i should apply..
Is the commit in #1 already supposed to be in code? Or should I apply the patch in #4? Or not apply the patch based on the comment in #6?
Well, i applied the patch in #4 and it fixed the issue of the html being printed to the screen.
However, I am still not getting a timeago type of date format. It still just has regular date and time.
Is this a related issue, or should i file a new issue?
thanks.
Comment #8
cellar door commentedIf you take a look at #1996706: Timeago Patch Breaks functionality you'll see the js for timeago was removed in a patch recently. Putting those lines back into the module loads the helper js file and timeago works again.
Comment #9
devin carlson commentedThis issue is caused by AdaptiveTheme wrapping comments in a link back to the comment itself.
Patch to AdaptiveTheme with workaround for Commons Origins incoming...
Comment #10
devin carlson commentedFiled #2018081: Comment creation date links to same location as comment title against AdaptiveTheme.
Comment #11
stupiddingo commentedTested and marked #2018081: Comment creation date links to same location as comment title as RTBC. Same is true here I suppose?!
Comment #12
behoppe333 commentedNewbie question: When I drush make a fresh instance of dev release, I won't see this patch until its status changes from RTBC to Fixed. Correct?
I ask because my fresh instance of dev release has this bug, I'm new to this community, and I'm making sure I understand how patches flow via commits to the code that I pull with git.
Thanks for any corrections or affirmations :-)
Comment #13
devin carlson commentedA patch to include the fix from #2018081: Comment creation date links to same location as comment title.
Comment #14
devin carlson commentedCommitted #13 to Commons 7.x-3.x.
http://drupalcode.org/project/commons.git/commit/447147f