Ive written a plugin and released it into repository. When i first released it, I had no problem updating screenshots and updating the readme file contents. Now it seems as if the plugin host site wants to revert to the original readme file and the original screenshots. Can anyone help me?
Here is a link to my plugin
Here is a link to my SVN
I’m having the exact same problem, comforting to know I am not the only one!
In the WP-admin of my website the update shows up and once updated, it contains the new readme.txt but on wordpress.org the content of the readme.txt is not updated and still shows the info for the old version.
I ran my readme.txt through the validator and succeeded with ‘Flying colors’ so I don’t think something is wrong there.
okay great. Glad im not the only one. Im rather new to the plugin svn thing and when something like this happens it throws me for a loop. I guess we will just wait it out together lol. If you discover something, let me know please. =)
I know that there’s been a lot of server movement on wordpress.org over the past few days. This might have something to do with these problems. I’ve seen 1 or 2 others with the same problem. It could just a case of waiting for 24 hours to allow any mirrors etc to update but, just in case, I’ll flag this up to the attention of the Plugin team.
It’s been working for some people.
If you updated during the time we were upgrading servers, that may be why. When did you update the readme?
Your “Stable Tag” in the readme.txt is incorrect. You have it listed as 0.2.1 but there is no /tags/0.2.1 directory. If the plugin’s live version is in trunk, then the Stable Tag should be “trunk”. Stable Tag is actually a directory name, not a version number.
Your plugin has an incorrect directory structure. There should not be a subdirectory in /trunk, the plugin files and the readme.txt and everything else should be in the /trunk root itself.
Your Stable Tag is okay, but it’s likely that it can’t find it properly because of the readme.txt file not being located in /trunk.
Thanks for looking into it guys and girls!
The first commit I did was yesterday evening 20:52 CET+1 , the second 45 minutes later. Today I tried again at 12:22 and 16:25.
But if it’s just a matter of time, I’ll wait 24 hours.
But if it’s just a matter of time
It’s not a matter of time. If it doesn’t update within about 15 minutes, then it’s not going to update at all. Updates only happen when changes are made to the plugin’s repository.
Fix the readme.txt to have the correct Stable Tag.
Thanks Samuel/Otto for looking into it. I’ll work it out.
I have the same problem.
As far as I can see, my readme.txt has the correct stable tag:
I also updated my assests/* files yesteday (and they are correct here http://plugins.trac.wordpress.org/browser/acf-field-date-time-picker/assets), but in the plugin directory the previous ones are showing: http://wordpress.org/extend/plugins/acf-field-date-time-picker/screenshots/
I’m also having the same problem with http://wordpress.org/extend/plugins/plugin-organizer/. I have validated my readme file and everything is fine. I have had this plugin on wordpress.org for a couple of years and now it is suddenly not updating the plugin page. Something is wrong with the wordpress.org server.
Per Soderlind, your trunk readme says stable is 2.0.7
Jeff, your readme matches what I see on your plugin.
Yes, had to update my plugin. Everything looks fine after the new commit.
Took me a few hours but I finally succeeded!
I added all versions (0.1, 0.2 and 0.2.1) to the tag-directory, moved the screenshots from the trunk to the assets-folder (they weren’t showing up from day one).
Also I changed
Stable Tagin all the readme files.
I don’t know what did the trick but I’m happy it’s ok now. Thanks everyone!
It doesn’t match. When you go to the link in your comment you see up to version 2.6.2 in the changelog but the plugin page only shows up to 2.5.9 in the changelog. Both the readme in the trunk and tags/2.6.2 have the full changelog up to 2.6.2 but the plugin page at http://wordpress.org/extend/plugins/plugin-organizer/changelog/ does not.
You’re telling WP there that you’re using 2.6.2 🙂
- The topic ‘Plugin using old readme?’ is closed to new replies.