#11421 closed defect (bug) (fixed)
Comment Feed Dates All Wrong
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | 2.9 | Priority: | high |
Severity: | normal | Version: | 2.8.4 |
Component: | Feeds | Keywords: | has-patch tested |
Focuses: | Cc: |
Description
I realize 2.9 is almost out the door, but I'm hoping to pin down whether this is a core bug or something going on with a plugin ASAP.
When I hit /comments/feed/ on my site, the comments appear in the correct order, but every one of the pubDate values begins with "Sun, 13 Dec 2009" and I'm certain none of the listed comments were added today.
Attachments (2)
Change History (15)
#2
@
15 years ago
get_comment_time('Y-m-d H:i:s', true, false)
returns string(8) "06:42 PM"
Starting to look like a filter or plugin issue. What I need to know now is why it affects the comment feed and not the post feed....
#3
@
15 years ago
class Walker_Comment uses a completely different syntax for date output. That at least explains why my themes are working when the feed is not.
<?php printf(__('%1$s at %2$s'), get_comment_date(), get_comment_time()) ?>
#4
@
15 years ago
This discrepancy is my primary suspect now:
get_comment_time('Y-m-d H:i:s', true, false) get_post_time('Y-m-d H:i:s', true)
The post feed and comment feed are not using the "translate" parameters consistently.
#5
@
15 years ago
I was able to reproduce the bug in a test environment using the qTranslate "Date / Time Conversion" setting.
I still haven't ruled out the "translate" parameter as a possible cause though.
#6
@
15 years ago
- Keywords needs-patch added; needs-testing removed
It looks like qTranslate needs to hook get_comment_time() because it is being used in Walker_Comment for template output. get_post_time() is not used in that manner, so it is not hooked.
I'll get started on a patch to add date and time filters to Walker_Comment:start_el().
#10
@
15 years ago
These functions don't even have the same defaults?! *shakes head and stares at the screen blankly*
One of the calls inside start_el() has to be wrong then. Holy hell this is confusing.
So far I've ruled out:
This is going to be trickier to find than I had hoped.