Make WordPress Core

Opened 14 years ago

Closed 13 years ago

#15794 closed defect (bug) (duplicate) plugins pages not updating when readme.txt changes

Reported by: michelwppi's profile michelwppi Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Site Keywords: plugins repository
Focuses: Cc:


Just for infos or actions in plugins repository:
Last saturday and sunday, I updated 3 plugins with new current versions.
Curiously the download button (and zip) was correctly updated but not the Last Updated Date and the displayed readme and tabs. This monday morning, the refreshing of readme displaying works again but the last updated date is not in accordance with the trac date log when the new tag folder and trunk readme were inserted yesterday or saturday.

Best regards

Change History (7)

#1 @ocean90
14 years ago

  • Component changed from General to site

#2 @nacin
14 years ago

  • Milestone changed from Awaiting Review to

#3 @solarissmoke
13 years ago

  • Summary changed from issues in Last Updated Date in Plugins Repository to plugins pages not updating when readme.txt changes

I'm seeing the same problem. The content of plugins pages on my recently updated plugins do not reflect the content of the readme file.

E.g: links to "Download version 1.3" but the changelog (which was updated) still only shows 1.2, and the main page also hasn't changed.

readme file:

It appears that changes to readme.txt are being ignored.

#4 @jquindlen
13 years ago

I'm having the exact same issue as well. Here's my example.

The download link is for version 2.1.1:

However the readme.txt is being pulled from 2.0.13 which is 2 versions out of date. Here's the correct readme.txt

And I can also confirm that the updated date is incorrect. I updated today, 01/26/11 and it shows the last update as 12/08/10

#5 @eventualo
13 years ago

Same problem. I updated yesterday (23 feb 2011) but it shows date of previous update yet (14 nov 2010). Here my plugin:

Last edited 13 years ago by eventualo (previous) (diff)

#6 @duck_
13 years ago

This is a problem with the order of operations. If you want to see an update to the plugin page then just commit some trailing whitespace to the trunk readme.txt. See #16522, and a few other duplicates out there I think which could all be merged.

#7 @scribu
13 years ago

  • Milestone deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Closing as dup of #16522, since it's clearer.

Note: See TracTickets for help on using tickets.