Last night I spoke at a meetup of the Cape Town PHP Group. I was speaking alongside the excellent Gareth McCumskey who was giving a run down of what we can expect in PHP 7 (we can expect a lot of awesomeness by the way – you should really check that out). My presentation for the evening was a primer on WordPress development and a guide on how to bend WordPress to your will (which would have made a way more awesome title for the talk).
Today is not only my 3 year anniversary of joining WooThemes, but it also marks the first day that I am no longer a full-time developer on the team. This kicks off a significant new chapter in my professional career as it will be the first time since I started working that my job will no longer be 100% focussed on writing software.
My new title at WooThemes is Community Engagement Manager.
In the early ’80s, my father trained countless Cobol programmers. Today I write WordPress plugins, but there’s one thing that our work has in common.
As part of a recent Sensei update we added some custom capabilities to the editor role, but we discovered that some people have deleted that role from the database as a way of cleaning up unused data on their sites. This meant that our add_cap() calls were causing fatal errors for these sites. Here’s how we solved this problem for ourselves.
With Seriously Simple Podcasting crossing 35,000 downloads and v1.8 of the plugin being released recently it was high time that I put together complete documentation for it. After spending some time building the site that you can now find on my new docs subdomain I thought it would be valuable to share the tools I used for posterity. Here you will find the theme and plugins that I used to get my docs site up and running.
Once you have more than a couple of plugins in the WordPress plugin repository, it can become rather cumbersome to manage them all effectively. This problem is particularly accentuated when a new version of WordPress is released and it becomes a chore just to keep tabs on which version your plugins all support. At least that’s what happened to me when WordPress 4.1 was release recently.
This is why I created Plugin Dashboard.
The other day I posted about showing plugin developers appreciation and how it’s actually really easy to do. The problem, as was pointed out to me, is that writing reviews, donations, etc. are all only accessible from the plugin page on the repo and there’s no quick way to get there from the WordPress dashboard. All is not lost, however! It is possible to add custom links to the plugin list table alongside the default links that point to the author’s website and the plugin details page.