Tagging new plugin version issues
According to http://wordpress.org/extend/plugins/about/faq/ updating my readme.txt file is the way to tag a new version.
However, my plugin http://wordpress.org/extend/plugins/events-manager/ had 4.16 in the readme, yet it updated because the trunk events-manager.php had 4.17
Is this a bug or something I should avoid doing? Important as I was planning on having incremental dev versions on the trunk, this’ll prevent that so would have to find another way.
Can I specify what version of my plugin the WordPress.org Plugin Directory should use?
Yes, by specifying the Stable Tag field in your trunk directory’s readme file.
If you change the Stable Tag, you are saying ‘This version is the one to use.’
If you look at your readme.txt in trunk it says “Stable tag: 4.171”
sorry, wanted to mention this after changing it but it slipped my mind… long day.
the text file was at http://plugins.trac.wordpress.org/browser/events-manager/trunk/readme.txt?rev=437508 state, and my events-manager.php file was changed to http://plugins.trac.wordpress.org/browser/events-manager/trunk/events-manager.php?rev=440345 yesterday.
today, I came to find that the plugin current version was 4.17 when it was not what the readme.txt said (should have remained at 4.16). A few people had issues because there were some untested conflicts.
You’ll see the next readme revision wasn’t changed until today, which is to reset the version to one with a tagged folder in the repo.
hope that makes sense!
Interesting… I’ve made changes like that a dozen times and never seen that happen. I’m going to play with this.
did you manage to check this out Ipstenu?
not directly related but may have something to do with the same issue:
I’m wondering if my plugin folder has issues, because I tagged version 4.18 last week and some blogs aren’t updating. It’s pretty random too it seems because I’m checking blogs on the same server even and one works whilst the other doesn’t.
This is compounded because my pro plugin works off the main plugin, and this update needed both to update, so quite a few confused users when they see php warnings after updating the pro version.
I came up blank. I would email plugins[at]wordpress.org to ask if something got munged in the DB. Or consider a ‘fake’ update to get everything all even at a new version (4.2) and see if that cleans it out?
I can make an update today, so will do that and see. thanks.
fyi, updated to 4.2 and still not working, have emailed plugins[at]wordpress.org about this
Just to be clear, it shows as 4.2 on the plugin page, AND in the trunk readme: http://plugins.svn.wordpress.org/events-manager/trunk/readme.txt
So … what are we calling ‘wrong’ now?
maybe I should have started a new thread to save confusion 🙂 first five comments are pertinent to a different problem, which is to do with just changing the version number in events-manager.php.
this is the same problem as recently with 4.18, it shows as 4.2 is the latest version but it doesn’t actually come up on the automatic updater on many (more than 50% i think) blogs.
tested this on various servers, shared, vps etc. with random installs, it’s also very random as some sites do show an update, others don’t (other updates seem fine).
Mark wrote back, so hopefully he’ll be able to help too.
I replied to you via email already, but I’ll post it here so that everybody knows too.
Version numbers are not decimal numbers.
By the PHP standardized convention, version 4.2 is lower than 4.18.
Version numbers are independent integers, that just happen to be connected by dots.
True, in version numbers:
4.2 < 4.18
4.20 > 4.2
4.2.1 > 4.2
4.2.3 < 4.20
Get it? The version_compare is telling the system that 4.2 is not an upgrade to 4.18, so they’re not going to get notified and they won’t upgrade.
Change your version number to be higher than 4.18. Then they’ll get an update.
BTW, You already messed up your version numbering something royal with that 4.171 version. To get those sites to update, you’ll have to go higher than that, like with version 4.172 or 4.180 or something.
Might as well just switch to version 5.0 and then start using version numbers correctly to begin with.
Also, before anybody says anything, yes, WordPress itself is doing version numbering wrong. I know this.
However, the way WP is doing it wrong fits into the PHP standardized scheme too. In WP, 2.9 was followed by 3.0. However, there was also a 2.9.1 and such too. Personally, I would have gone to 2.10 instead, but that’s just my opinion.
that’s good to know. i’ll go with 4.210 tomorrow as there’s a major change coming soon that’ll justify the 5 status.
thanks for the help!
I’ve never gone past single digits. Interesting, but that makes sense, really. 4.20 would have been fine then.
- The topic ‘Tagging new plugin version issues’ is closed to new replies.