WordPress.org
Get WordPress

Make WordPress Core

Opened 17 years ago

Closed 17 years ago

#9566 closed defect (bug) (fixed)

lastBuildDate should be used in rss/channel instead of pubDate

Reported by: peaceablewhale's profile 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 17 years ago.

Download all attachments as: .zip

Change History (8)

@peaceablewhale
17 years ago

#1 @peaceablewhale
17 years ago

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

#2 @peaceablewhale
17 years ago

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

#3 @peaceablewhale
17 years ago

Correction: Not #9577, should be #9567

#4 @Denis-de-Bernardy
17 years ago

does the spec say either elt is required?

#5 @peaceablewhale
17 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.

#6 @Denis-de-Bernardy
17 years ago

  • Keywords tested commit added

+1 then

#7 @ryan
17 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.