PUBLISHED and UPDATED in Atom feeds
ahoeben - June 25, 2006 - 14:27
| Project: | Drupal |
| Version: | 7.x-dev |
| Component: | aggregator.module |
| Category: | bug report |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I am encountering PUBLISHED and UPDATED attributes in some Atom feeds, instead of CREATED and MODIFIED.
Attached patch adds support for these variations.
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| aggregator-atomdates.patch | 796 bytes | Ignored | None | None |
#1
I can't find that in the Atom 0.3 specification:
http://www.mnot.net/drafts/draft-nottingham-atom-format-02.html#rfc.sect...
However, in this version of the Atom specification, I can:
http://www.atompub.org/2005/08/17/draft-ietf-atompub-format-11.html
More information at:
http://www.intertwingly.net/wiki/pie/PaceDateModified
It looks like both dates can be present. What happens when that is the case? The date handling isn't up to sniff; maybe we should do $date = max($date_issued, $date_created, $date_modified, $date_updated, ...) ?
#2
I committed your patch (it's an improvement) but I'm leaving this as 'code needs work' so we can investigate this some more, and come up with a more complete solution.
#3
To be honest, I did not look at the atom spec. I was just responding to what aggregator was encountering 'in the wild'.
In the rationale on http://www.intertwingly.net/wiki/pie/PaceDateModified , it is somewhat implied that if atom:updated changes, atom:modified must certainly have changed as well. So atom:modified should always have the most current date.
The current patch first looks for atom:modified, and ignores atom:updated if atom:modified is found. Having said that, aggregator currently first looks for an issued/created date, and ignores updates. For node we have both a 'created' and 'changed' timestamp, but for aggregator we don't. But that would be a bigger patch/issue at the moment
#4
This patch is applies?? Feature requests go to the current development version...
#5
This is fixed in DRUPAL-5.
#6
Automatically closed -- issue fixed for two weeks with no activity.