This post suggests a simple trick that will enable you to update a plugin to the latest version when it already thinks it’s at the latest version. It’s taken me a few months to realise this. Every now and then I have some changes that I want to apply to my oik plugin. I make the changes locally and test them on my Windows machine, then I apply them to SVN, extract the latest .zip file and upload it to a test site. In order to do this I first need to rename the plugin on the test site, because otherwise WordPress does not allow me to upload the plugin… it says it’s already installed. This of course breaks the site temporarily. And with oik currently having multiple child plugins WordPress produces some interesting messages until everything’s reconfigured.
Well just now I realised that oik-plugins was not at the absolute latest level of version 1.10. So I was just about to go through the rigmarole of rename, upload and reactivate when I thought
Why not just change the version of the base plugin to an out of date one?
And that’s what I duly did. I edited the currently installed oik.php to set the version to 1.9a and when I was offered an upgrade to 1.10 I chose it.
TADA. So now I can get back to oik-plugins to continue documenting the
- WebP on WordPress and old browser support
- Internationalizing and localizing block based plugins
- Migrating block based plugins from webpack to wp-scripts
- oik-magnetic-poetry v0.2.2
- Computing not Chemistry at Imperial College
- IBM retirement age ( 63 ) – I’ve reached it!
- My Favourite Theme
- Now what’s going on?
- Show and tell – What’s going on?
- Slog – server performance testing