Title: Plugin Directory Not Reading Version
Last modified: August 19, 2016

---

# Plugin Directory Not Reading Version

 *  [athenaofdelphi](https://wordpress.org/support/users/athenaofdelphi/)
 * (@athenaofdelphi)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/plugin-directory-not-reading-version/)
 * Hi all,
 * I’m hoping someone can help with this, and that it’s in the right place.
 * I uploaded a new version of my plugin weeks ago. The plugin directory failed 
   to pickup the version number correctly and now, several releases later (mainly
   releases trying to fix the problem), it still isn’t reading it correctly.
 * I’ve validated the readme, re-encoded the files as ASCII, checked and double 
   checked everything I can think off and everything that I’ve been able to find
   here about the same issue.
 * Unless I’ve misunderstood or made a complete booboo, I can find no reason why
   my plugin isn’t properly recognised by the directory. I’ve mailed the plugin 
   team about it and so far, the only response has been that the directory is not
   picking up the version number correctly, have I got the version number in the
   header? The directory is picking up the version number (I’m guessing from the
   tagged versions) but it is not recognising this as the latest stable version 
   and consequently nothing is recognising there is an update available for the 
   widget.
 * If anyone more experienced than me could take a look at the files and point me
   in the right direction, I would greatly appreciate it as I have exhausted my 
   limited knowledge of the plugin directory/repository.
 * The widget is at [http://wordpress.org/extend/plugins/advanced-custom-field-widget/](http://wordpress.org/extend/plugins/advanced-custom-field-widget/)
 * Regards
 * Christina

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

 *  Anonymous User
 * (@anonymized-3085)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/plugin-directory-not-reading-version/#post-1806556)
 * looks ok to me as well. It shouldn’t make a difference but the example readme
   has values like this:
 * > Requires at least:
   >  Tested up to:
 * as opposed to all upper case like you have, might be worth changing it to see
   if that fixes things. In theory it shouldn’t, but I can’t think of anything else,
   sorry.
 *  Thread Starter [athenaofdelphi](https://wordpress.org/support/users/athenaofdelphi/)
 * (@athenaofdelphi)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/plugin-directory-not-reading-version/#post-1806572)
 * Thanks for the suggestion Rich, it’s confusing the hell out of me. I’ll give 
   that a try later on when I get home from work.
 *  Thread Starter [athenaofdelphi](https://wordpress.org/support/users/athenaofdelphi/)
 * (@athenaofdelphi)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/plugin-directory-not-reading-version/#post-1806744)
 * Well, I released a translation, updated versions and edited the files with headers
   so they weren’t all uppercased.
 * The version shows up in the directory, but is not recognised as the latest version
   and the plugin installed on my blog isn’t recognising there is an update, so 
   thanks for the suggestion Rich, but it’s not fixed it.
 * I’ve just checked the headers and files against previous versions which worked
   and I just can’t see anything wrong 🙁
 * Is there anyone else reading who may now how to fix this?

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

The topic ‘Plugin Directory Not Reading Version’ is closed to new replies.

## Tags

 * [not recognised](https://wordpress.org/support/topic-tag/not-recognised/)

 * 3 replies
 * 2 participants
 * Last reply from: [athenaofdelphi](https://wordpress.org/support/users/athenaofdelphi/)
 * Last activity: [15 years, 6 months ago](https://wordpress.org/support/topic/plugin-directory-not-reading-version/#post-1806744)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics