[ php-blog-Bugs-1461728 ] pubDate fluttering in RSS2.0 feeds

Bugs item #1461728, was opened at 2006-03-30 18:05
Message generated for change (Comment added) made by jgoerzen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=542822&aid=1461728&group_id=75065

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Syndication Feeds
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: John Goerzen (jgoerzen)
Assigned to: Nobody/Anonymous (nobody)
Summary: pubDate fluttering in RSS2.0 feeds

Initial Comment:
I've noticed a good deal of strangeness in the behavior
of some syndicators that are pulling from my site. 
I've tracked the behavior down to the pubDate field.

In this report, I am talking about the main RSS 2.0
feed, not the one that lists comments; that is, the
feed you could find at
http://changelog.complete.org/feeds/index.rss2.

Serendipity is taking the pubDate field to mean "date
of last comment post" rather than "date of post of
article itself."  This is not really correct.

In fact, I verified this behavior.  I saved off a copy
of the feed, posted a copy, and saved off another copy.
 The diff is attached.

Now, as for why this is happening... I don't know.  The
article publishing date on the website for the blog
itself remains correct all the time.  Only the feed
seems to be impacted.

Just in case, I tried reverting my earlier patch for
the regex patch, and go to a more supported URL scheme,
but that made no difference.

----------------------------------------------------------------------

>Comment By: John Goerzen (jgoerzen)
Date: 2006-03-30 22:15

Message:
Logged In: YES 
user_id=491567

One thing I missed when I looked at that diff was that the
pubDate field that is fluttering is the channel one and not
the story one.

But that makes it stranger, because in the plugin
configuration for the Syndication plugin, I had already set
the field "pubDate" to "No".  So it shouldn't even be
including a pubDate at the channel level -- only on the
story level.

Funny thing is -- if I go into that same config screen and
set the pubDate to Yes, then that per-channel pubDate is
ommitted.  So I think there is just a logic error someplace
that is swapping around this one.

So that's bug #1.

Bug #2 is that this item is coming from the last_modified
field instead of timestamp (as all the other pubDates for
items are coming from), on line 1000 of plugin_internal.inc.php.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=542822&aid=1461728&group_id=75065


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642