Oh my. It’s been a long time since I’ve felt such hate from users. What horrendous thing did I do? I change one of my plugins so that it now required PHP 7 to work, instead of 5.3. You know PHP 7… which itself goes out of support in the next few months. PHP 7 […]
I recently updated my Plugins List plugin and the minimum PHP level requirement moved from 5.6 to 7. Let me explain my reasoning and what my plans are for PHP support.
Don’t you just hate it when WordPress plugins are just a rule to themselves when it comes to adding new menus to your installation? Those slick, and well thought out, menu positions are now, seemingly, randomly dotted with plugin menus jostling for attention. Well, hate no more. Tidy My Menus is an automated solution to […]
A WordPress plugin, named No Self Pings, has been around since, seemingly, the dawn of time (2006). Indeed, Matt himself added it to the SVN repository. Since it’s release it’s only had one update (in 2007) and, more recently, has been plagued with users reporting that it didn’t work anymore. And then, yesterday, this happened…
I'm happy to announce my latest WordPress plugin – Pride Bar. My first plugin available, straight-away, from both WordPress.org and Github, this adds the Pride rainbow to your boring admin bar… At the moment activation will add the Pride bar to all users. If you think I need to add an option where individual users […]
Today marks a momentous occasion – for most of this year I’ve been trying to bring my 18 WordPress plugins up-to-date and, as of this morning, it’s now complete. You see, I’d allowed my WordPress plugins to fall behind in their updates, for various reasons, and changes were required to them all – not enhancements […]
Now that the WordPress plugin README supports a minimum PHP level, I thought it was time to dust down my guide to the data that you can add to the README and the plugin header. This also documents how to extend this further, adding additional fields easily to the plugin meta displayed upon installation.
Please, take a read and let me know of any feedback you may have.
The WordPress.org plugin directory has had a massive overhaul and, as a result, plugin information is now shown differently to before. For plugin developers, therefore, a tweak to how you present your README (and associated assets) can ensure your plugin is presented better.
Don’t panic, I’m still supporting them 😉
However, I’ve realised that I’m doing a lot of work to maintain backwards compatibility for quite old versions of WordPress. But why?
“WordPress plugin developer admits he pushes out code changes without incrementing the version number. Discuss”. This is how this started off.