It’s a couple of days early but given that Christmas is on a Sunday this year, it seems to make sense to say this today rather than sometime during the weekend.
Especially since most of us will be spending time elsewhere than on this blog, right? 😎
Software Engineering in WordPress, PHP, and Backend Development
Notes on programming-related problems that I’ve encountered while working on various projects.
It’s a couple of days early but given that Christmas is on a Sunday this year, it seems to make sense to say this today rather than sometime during the weekend.
Especially since most of us will be spending time elsewhere than on this blog, right? 😎
If you’re working with PHP CodeSniffer in your WordPress project, then you’re likely familiar with how much time it takes to complete indexing all PHP files.
You start up your IDE, configure PHPCS, point it to your set of WordPress rules, and then wait for it to begin doing its job. Don’t get me wrong: I love having it sniff the code while writing it, but it also takes a bit of time for it to finish parsing it.
Stop PHPCS From Indexing All PHP Files.
Granted, this is true of likely any PHP-based project, but how many of those do I write about here? 🙂
We’re celebrating Thanksgiving in the United States today. If you’re doing the same, Happy Thanksgiving!
Meghan did an awesome job with the table – if was left to me, there’d be no photo. :)
If not, I hope your day is going well and that maybe you’ve still got a thing or two or nine for which to be thankful. 🙂
For those who have read my Atom and WordPress Coding Standards post, then you should have everything you need when it comes to setting up the editor to evaluate your code with the WordPress Coding Standards.
Recently, though, the 0.10.0 release of the coding standards were published on GitHub, and it brings a lot of changes.
If you’re looking to begin upgrading to this new change, there’re a few caveats that you may experience when working with Atom and the WordPress Coding Standards.
They’re easy to address, though.
In the previous post, I started walking through what we need to do to display custom messages in WordPress. This is specifically in the case of when we are opting to use something other than the Settings API.
In the previous post, I covered the following:
To follow-up with what was previously covered, I’ll show how to render these messages – regardless of if they are error messages, notices, or success messages – on the administration page.
© 2025 Tom McFarlin
Theme by Anders Noren — Up ↑