Support » Plugins » Hacks » "Last Upated"

Viewing 4 replies - 1 through 4 (of 4 total)
  • Is .65 the latest version of the plugin? Did you update the readme file with your release? Not sure what the root cause is but I usually update the readme and meta data in the plugin main file and it picks up the change within 15 minutes (WordPress’s plugin refresh rate).

    I’ve had the same problem with my own plugin. Last summer when I uploaded v1.1.3, the “Last Updated” date correctly updated fine.

    Earlier this month when I uploaded v1.1.4, the Last Updated date remained/s stuck at last summer’s date. The updated plugin does indeed show/list properly as 1.1.4, and downloads properly too. The pie graph showing the breakdown of versions also reflects correctly.

    Did I update readme.txt? Sort of. I update that separately from plugin version upgrades, since I just need to declare that the latest version of WP works with my plugin (“Tested up to” line).

    I wonder if the cause is this… I use the “Trunk Method” whereby I always have the latest/current plugin version in the trunk folder. In other words I don’t retain and tag past releases. In readme.txt I have “Stable tag: trunk”. Maybe the Last Updated field looks for a change in that line?


    Edit. I just found this post. A moderator says it’s a known issue happening to many other people as well. It’s in queue.

    Just a polite bump to see if any progress has been made on this issue…

    For anyone following this thread…

    I think this problem is old news. I recently committed some changes to the readme.txt of my plugin (updating WP version compatibility) and in doing so it updated the plugin’s ‘Last Updated’ date published in the WP Plugin Directory. So, I consider this evidence of problem solved. (Thanks, WordPress folks!)

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘"Last Upated"’ is closed to new replies.