This post is the result of about 3 or 4 hours of Googling! There are so many false trails out there that I almost gave up, but I managed to work out how to do this most impossible of things:
Restart Apache from the command prompt (Git Bash, CMD.EXE, batch file) on Windows 10, without receiving the "Do you want to allow this app to make changes to your device" prompt:
So… Let’s just say for a moment, that you borked your plugin by accidentally tagging the whole repo. Never going to happen, right, because we all use deployment scripts, don’t we?
I’ve been using using and developing on WordPress for almost 10 years. In all that time, the single most important (WordPress related) thing to happen to me was WordCamp Gold Coast 2011, which was held 5 years ago today.
Today marks two years since I joined Envato. Those two years have disappeared in a whirlwind, with so much happening in that time. I decided to pause for a moment, to look back at some of the highs and the lows.
There is mounting excitement over the WP REST API being added to core and rightly so! It is going to fundamentally change the WordPress landscape and open up all sorts of new possibilities. Developers are drooling over all the cool stuff they are going to be able to build. Exciting times!
But…
When it comes to using the REST API with themes, it may not always be the best choice.
When WordPress 4.3 was released, it added the ability for users to set a site icon, also known as a favicon, in the Customizer. In the past, users had to either add this manually, through a plugin, or through the theme options (if their theme included this functionality).
In this post, I’m looking at the last of those scenarios. What should theme authors do now that WordPress itself offers the equivalent functionality?
I’m writing this post because of the very sad passing of Kim Parsell, but it’s not going to be about her. Much has already been said by people who knew her far better than I. Continue reading
Recently, there has been some discussion around whether Jetpack is bloated. Hmm, actually, we’ve been talking about that for years… Anyway, the interesting part to me isn’t whether Jetpack is bloated, it’s why Jetpack is bloated.
Scary post title right? Well, I wish it was link bait, but it’s not. This is really serious.
Yesterday, it was announced that there was a critical security vulnerability with versions 3.0 to 3.9.2 of WordPress.
Continue reading
If you create free WordPress plugins then you almost certainly host them on the official WordPress Plugin Directory. You probably also have a home page for them on your own site. But that means keeping both the readme.txt file and your own site up to date with changes. Hassle…
Continue reading