Title: Plugin directory “Last Updated” not changed after initial commit?
Last modified: August 20, 2016

---

# Plugin directory “Last Updated” not changed after initial commit?

 *  [Jan Fabry](https://wordpress.org/support/users/janfabry/)
 * (@janfabry)
 * [15 years ago](https://wordpress.org/support/topic/plugin-directory-last-updated-not-changed-after-initial-commit/)
 * I released the first version of [my Rewrite analyzer plugin](http://wordpress.stackexchange.com/questions/3606/a-tool-to-analyze-rewrite-rules/3608#3608)
   with [a commit on 2010-05-12](http://plugins.trac.wordpress.org/log/monkeyman-rewrite-analyzer/).
   The WordPress.org plugin directory however [still displays 2010-11-27 as the “Last Updated” date](http://wordpress.org/extend/plugins/monkeyman-rewrite-analyzer/)–
   this is the date when the plugin directory was created in the repository.
 * [The Developer FAQ](http://wordpress.org/extend/plugins/about/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](http://wordpress.org/extend/plugins/file-commerce/)
   in other plugins [that were committed more than one day after the directory was created](http://plugins.trac.wordpress.org/log/file-commerce/).
 * 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](http://wordpress.org/support/topic/plugin-last-updated-time-not-getting-updated?replies=8):
 * >  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](http://wordpress.stackexchange.com/questions/18235/plugin-directory-last-updated-not-changed-after-initial-commit).
   I will update both places with new info._

Viewing 6 replies - 1 through 6 (of 6 total)

 *  [esmi](https://wordpress.org/support/users/esmi/)
 * (@esmi)
 * [15 years ago](https://wordpress.org/support/topic/plugin-directory-last-updated-not-changed-after-initial-commit/#post-2099784)
 * Please contact [plugins@wordpress.org](https://wordpress.org/support/topic/plugin-directory-last-updated-not-changed-after-initial-commit/plugins@wordpress.org?output_format=md)
 *  Thread Starter [Jan Fabry](https://wordpress.org/support/users/janfabry/)
 * (@janfabry)
 * [15 years ago](https://wordpress.org/support/topic/plugin-directory-last-updated-not-changed-after-initial-commit/#post-2099858)
 * I have sent a mail to the plugins team. I think this has been reported in the
   Trac as [Plugins display incorrect update date](http://core.trac.wordpress.org/ticket/16266).
 *  [Tommy](https://wordpress.org/support/users/akisbis/)
 * (@akisbis)
 * [15 years ago](https://wordpress.org/support/topic/plugin-directory-last-updated-not-changed-after-initial-commit/#post-2099860)
 * I noticed the same issue… And the blogs are never notified with the new version:/
 *  [Robert Chapin](https://wordpress.org/support/users/miqrogroove/)
 * (@miqrogroove)
 * [15 years ago](https://wordpress.org/support/topic/plugin-directory-last-updated-not-changed-after-initial-commit/#post-2099908)
 * I’m having this same problem. My plugin dates are wrong.
 *  Moderator [Samuel Wood (Otto)](https://wordpress.org/support/users/otto42/)
 * (@otto42)
 * WordPress.org Admin
 * [15 years ago](https://wordpress.org/support/topic/plugin-directory-last-updated-not-changed-after-initial-commit/#post-2099940)
 * > 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.
 * [otto@wordpress.org](https://wordpress.org/support/topic/plugin-directory-last-updated-not-changed-after-initial-commit/otto@wordpress.org?output_format=md)
 *  [Robert Chapin](https://wordpress.org/support/users/miqrogroove/)
 * (@miqrogroove)
 * [14 years, 11 months ago](https://wordpress.org/support/topic/plugin-directory-last-updated-not-changed-after-initial-commit/#post-2099973)
 * Still having this problem. E-mail sent.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Plugin directory “Last Updated” not changed after initial commit?’ is
closed to new replies.

 * 6 replies
 * 5 participants
 * Last reply from: [Robert Chapin](https://wordpress.org/support/users/miqrogroove/)
 * Last activity: [14 years, 11 months ago](https://wordpress.org/support/topic/plugin-directory-last-updated-not-changed-after-initial-commit/#post-2099973)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics