Software Engineering in Web Development, Backend Services, and More
One of the things that I like about using Atom is that you’re really able to make the editor your own through its settings, packages, themes, and so on.
It’s not altogether different from WordPress, right? Sorry. That’s like some sort of shameless promotion or something.
Back to the point: One of the features I’ve missed when coming from another IDE is the ability have the automatic generation of DocBlocks.
And that’s where Docblockr comes into play.
Many of you are likely familiar with Office Hours with Carrie Dils. But if not, here’s what the show is all about:
Every Thursday at 2p ET as Carrie interviews a variety of folks within the WordPress ecosystem, from plugin developers to marketers to business owners. The one thing they have in common? Each guest has found business success through leveraging WordPress as both a tool and a platform.
I had the honor of appearing on the show in previous episodes and had a great time. I also recommend tuning in when you have a chance as it’s a great, free opportunity to hear and learn from others.
Weeks ago, Carrie celebrated her 100th episode (which is an awesome feat in and of itself).
We talk a lot about the idea of having bootstrap files in WordPress plugins, which I think are great, but we seem to limit it to those files that are responsible just for starting our WordPress plugins.
This isn’t exactly what I meant, but I dig the picture.
I mean, hooking into plugins_loaded and then instantiating some classes, setting up a service registry, or things like that are important. But what about other components that make up our plugins?
And by that, I mean what about our JavaScript files? Should they have their way to be bootstrapped?
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.
When working with the Settings API (or any other API that handles options, serialization, validation, and page redirections), dealing with custom messages in WordPress isn’t something that we typically have to worry about it.
The API takes care of all of that for us, and if we need to use other pieces of information, like the query string, we’re able to take advantage of API functions like get_query_var to check for the presence of a given value without much thought for how it was added in the first place.
But what about when you’re working on your administration page, and you need to display custom messages in WordPress after a redirect?
Kinsta offers premium managed WordPress hosting for everyone, small or large. Powered by Google Platform and strengthened by Cloudflare, they take performance to the next level. All hosting plans include 24/7/365 support from their team of WordPress engineers. Get started with a free migration today.
© 2026 Tom McFarlin
Theme by Anders Noren — Up ↑