WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 2 months ago

#24200 closed defect (bug) (fixed)

Plugin changelog does not update after checkin

Reported by: webaware Owned by:
Milestone: WordPress.org Priority: normal
Severity: normal Version:
Component: WordPress.org site Keywords:
Focuses: Cc:

Description

I checked in a new version (1.1.0) of plugin Gravity Forms DPS PxPay today, and after some hours the changelog has not updated.

http://wordpress.org/extend/plugins/gravity-forms-dps-pxpay/changelog/

Looking at the readme file in SVN, I can see the latest version which shows the updated changelog:

http://plugins.svn.wordpress.org/gravity-forms-dps-pxpay/tags/1.1.0/readme.txt

Downloading the current version (1.1.0) from the plugin page gives me the latest package, with the updated readme file.

Overly aggressive caching, or broken changelog update?

Change History (9)

#1 @SergeyBiryukov
4 years ago

  • Milestone changed from Awaiting Review to WordPress.org

#2 @sergej.mueller
4 years ago

Same problem here. The new plugin version has been uploaded, but the changelog has old data.

#3 @webaware
4 years ago

This also affects the changelog seen when viewing details of a plugin with an update, from any WordPress installation. Thus, anyone with v1.0.1 of Gravity Forms DPS PxPay sees that there is an update available, clicks "View version 1.1.0 details", and is presented with the changelog as it was at version 1.0.1 (and the info box says Version 1.1.0).

#4 @Otto42
4 years ago

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

This happened because you did the check in at the time when the SVN was being moved around. I gave it a kick, and your changelog is correct now.

#5 @webaware
4 years ago

Thanks Otto. I thought that happened on the 24th? I checked in on 26th (Aussie time), so I figured I would have been clear. Oh well, thanks for the fix.

#6 @mangeshp
2 months ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Same problem here. I am facing the same issue. I have released the two plugins and for both of them version number got updated, but the change log was old. I had to push a new dummy commit for the readme.txt file to see the change log updated.

Here you can see the commit history:
https://plugins.trac.wordpress.org/browser/transcoder/tags#1.0.7

Same thing happened with the other plugin.

#7 @Otto42
2 months ago

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

The changelog does not update at the same time as the version number. We have multiple servers. Only one of them can update the description of the plugin, including the changelog. Not all of them update at the same time.

#8 @mangeshp
2 months ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Ye, I am aware of this situation that it takes some time to update the change log and plugin description. But this has happened for the first time with me and for both of the plugins I released.

I almost waited for more than 25 minutes to check the updated change log, but change log didn't change so I had to push the extra dummy commit. Once I pushed the dummy commit on SVN, the change log got updated immediately.

You can check the SVN repo for the other plugin: https://plugins.trac.wordpress.org/browser/buddypress-media/tags#4.1.6

This has happened never before. It's quite strange coz the same thing happened with the both plugin we released.

#9 @Otto42
2 months ago

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

Please do not reopen this ticket again. if there is an issue, then it is not the same issue as this ticket.

It is certainly possible for a commit to be missed if the commit occurs while SVN is having load issues. In such a case, a dummy commit made later will fix the problem, or you can ping one of us in Slack to take a look at it.

However, these are known issues which only happen rarely, and not related to this three year old ticket.

Note: See TracTickets for help on using tickets.