Plugin directory “Last Updated” not changed after initial commit? (7 posts)

  1. Jan Fabry
    Posted 5 years ago #

    I released the first version of my Rewrite analyzer plugin with a commit on 2010-05-12. The WordPress.org plugin directory however still displays 2010-11-27 as the "Last Updated" date - this is the date when the plugin directory was created in the repository.

    The Developer FAQ states:

    Last updated time

    Time of last check in to the appropriate directory (trunk/ or the stable tag directory) after a version number change.

    Most developers commit their first version right after their plugin directory gets created, so you won't notice the difference. But I have seen the same discrepancy in other plugins that were committed more than one day after the directory was created.

    I committed both the trunk/ and tags/1.0/ directories in one go (with a local copy and then a commit), but the other plugin with this problem did it like most people do: a commit of trunk/ and then a remote copy to tags/1.0/.

    Otto recently said:

    The only time the readme gets parsed and the entry gets rebuilt is when the version of the plugin changes. However, for people using tags, this generally happens after they make the new tag and update the Stable Tag.

    The readme file got parsed, so I don't know what else I could have done to make it update correctly?

    This question was also asked at the WordPress Stack Exchange. I will update both places with new info.

  2. esmi
    Forum Moderator
    Posted 5 years ago #

    Please contact plugins@wordpress.org

  3. Jan Fabry
    Posted 5 years ago #

    I have sent a mail to the plugins team. I think this has been reported in the Trac as Plugins display incorrect update date.

  4. Tommy
    Posted 5 years ago #

    I noticed the same issue... And the blogs are never notified with the new version :/

  5. Robert Chapin
    Posted 5 years ago #

    I'm having this same problem. My plugin dates are wrong.

  6. I noticed the same issue... And the blogs are never notified with the new version :/

    This is not true. The version check in the update process does not use the Last Updated time, it only compares the version numbers.

    We know about the problem, and I've been trying to figure it out for months. So you can stop reporting it. Rest assured that when I find out what the problem is, I will fix it. The problem is just so random that it's hard to diagnose. By all rights and by the way the code is written, it simply shouldn't happen.

    If you have a plugin that won't update, my advice is to make a change to the readme.txt file (like add a space), commit, then wait half an hour. If that doesn't solve it, then email me directly with the link to the plugin, and I'll take a look.


  7. Robert Chapin
    Posted 5 years ago #

    Still having this problem. E-mail sent.

Topic Closed

This topic has been closed to new replies.

About this Topic