And it seems this bug persists
It was not a bug then and it is not a bug now. If a plugin has not been updated in 2 years, then that message appears.
If you want to make it go away, then update the plugin.
How exactly do I do that? Seriously, there are no changes required. It works fine. So do I just change the version number or…?
Why force an unneeded update? Why not make it so the author can manually tell the system that it’s OK without updating?
Or can I reupload the same version so users don’t get flagged to update their up to date plug in?
This seems so incredibly stupid to me, that I can only assume I’m missing something fundamental…
How exactly do I do that? Seriously, there are no changes required. It works fine. So do I just change the version number or…?
You know how the readme.txt file has a “Tested Up To” line with a WordPress version number after it? Well, if you’ve tested it with later WordPress versions and it works okay with them, then perhaps you should try updating that version number in that readme.txt file. You might be surprised at what happens.
If you’re using the /tags directory in the SVN, make sure you update the readme.txt in the tagged version too.
You don’t need to change the plugin itself, nor the plugin’s version number. And users won’t get an update if the version number of the plugin does not change.
Thank you, I had completely forgotten the Tested Up To tag.
