WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

#9566 closed defect (bug) (fixed)

lastBuildDate should be used in rss/channel instead of pubDate

Reported by: peaceablewhale Owned by:
Milestone: 2.8 Priority: normal
Severity: normal Version: 2.8
Component: Feeds Keywords: has-patch tested commit
Focuses: Cc:

Description

lastBuildDate is the equivalent of atom:updated in RSS 2. According to the RSS Best Practices Profile, "The channel's lastBuildDate element indicates the last date and time the content of the feed was updated" while "The channel's pubDate element indicates the publication date and time of the feed's content". Since the current timestamp is generated by get_lastpostmodified, lastBuildDate should be used instead.

Attachments (1)

9566.patch (799 bytes) - added by peaceablewhale 6 years ago.

Download all attachments as: .zip

Change History (8)

@peaceablewhale6 years ago

comment:1 @peaceablewhale6 years ago

  • Component changed from General to Feeds
  • Keywords has-patch added
  • Owner anonymous deleted

comment:2 @peaceablewhale6 years ago

The problem in feed-rss2-comments.php will be fixed in #9577.

comment:3 @peaceablewhale6 years ago

Correction: Not #9577, should be #9567

comment:4 @Denis-de-Bernardy6 years ago

does the spec say either elt is required?

comment:5 @peaceablewhale6 years ago

Both of the pubDate and lastBuildDate elements are optional, but the common practice is to use lastBuildDate (Blogger, Typepad, MovableType). The meaning of "lastBuildDate" is also more suitable here.

comment:6 @Denis-de-Bernardy6 years ago

  • Keywords tested commit added

+1 then

comment:7 @ryan6 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [11206]) Use lastBuildDate. Props peaceablewhale. fixes #9566

Note: See TracTickets for help on using tickets.