WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 3 years ago

#16266 closed defect (bug) (duplicate)

Plugin(s) display incorrect update date

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

Description

For example, the AddToAny plugin has been updated a couple times since 2010-11-2. For today's .9.9.7.3 release it should be displaying 2011-16-1, but it continues to display 2010-11-2.

Other plugins seem to be displaying the correct update dates.

Change History (8)

comment:1 dd323 years ago

  • Milestone changed from Awaiting Review to WordPress.org

comment:2 kawauso3 years ago

Plugin page now shows 2011-1-17, perhaps .org is just being a bit slow to update?

comment:3 micropat3 years ago

Well, version .9.9.7.4 was released hours after I reported this. You're right, the update date is correct now.

So unless this issue was fixed in wordpress.org manually or through a fixing release, it appears that back-to-back releases in the same day have seemingly 'jump-started' and corrected the update date.

comment:4 PeteMall3 years ago

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

comment:5 error3 years ago

  • Cc error added
  • Resolution worksforme deleted
  • Status changed from closed to reopened

This is still an ongoing issue. I now see it with Bad Behavior, and no amount of checking in anything seems to resolve the issue; it still states 2010-07-13 as the last updated date despite several releases in the last few months.

comment:6 janfabry3 years ago

  • Cc jan.fabry@… added

Maybe related: a first commit does not seem to change the "Last Updated" date, it stays at the date the directory for the plugin was created in the repository. Examples: File Commerce and my Monkeyman Rewrite Analyzer.

A bit more info on the WP.org support forums and the WordPress Stack Exchange.

comment:8 SergeyBiryukov3 years ago

  • Milestone WordPress.org deleted
  • Resolution set to duplicate
  • Status changed from reopened to closed

Let's focus on this in #16522 if there's still a problem.

Note: See TracTickets for help on using tickets.