[wp-meta] [Making WordPress.org] #185: Incorrect last_updated date in plugin API

Making WordPress.org noreply at wordpress.org
Sat Oct 5 07:34:34 UTC 2013

#185: Incorrect last_updated date in plugin API
  Reporter:  SergeyBiryukov  |      Owner:  coffee2code
      Type:  defect          |     Status:  closed
  Priority:  normal          |  Component:  Plugins Directory
Resolution:  fixed           |   Keywords:
Changes (by coffee2code):

 * status:  accepted => closed
 * resolution:   => fixed


 This issue has been fixed for the originally mentioned plugin and the less
 than two dozen others with the same issue.

 It looked like some sort of transient issue caused their last-updated
 dates to fail to set properly, so the UNIX epoch time (the default) was
 the result. Very few were affected and none have exhibited the issue in
 the few days since I fixed it. The plugins didn't share anything in common
 in terms of age, size, number or frequency of commits, number of tags,
 time of their last update, authors, etc.

 As for what was raised in comment [comment:2], that's a different issue.
 It looks at though the trac DB may have corrupted records for commits
 ranging from 10001 through 13076. Only trac seems to be affected. The
 plugin shown in the screenshot (http://wordpress.org/plugins/just-unzip/)
 has its plugin page properly generated and the code is available through
 SVN (http://plugins.svn.wordpress.org/just-unzip/). That warrants a
 separate ticket for systems to take a look at if anyone cares about those
 old commits through trac.

Ticket URL: <http://meta.trac.wordpress.org/ticket/185#comment:4>
Making WordPress.org <http://meta.trac.wordpress.org/>
WordPress blogging software

More information about the wp-meta mailing list