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.

Custom Messages in WordPress

In the previous post, I covered the following:

  • Looking at what happens when you use a safe redirect via one of the available WordPress functions,
  • Serializing custom error messages
  • Saving them to the database

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.

Read More

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.

Custom Messages in WordPress, Part 1

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?

Read More

/ July 20, 2016 / Comments Off on A Critical Update to Scheduled Post Shortcut?

A Critical Update to Scheduled Post Shortcut?

Based on active installs, ratings, and the like, Scheduled Post Shortcut isn’t what you’d call a popular plugin. Far from it, actually. But I’m okay with that.

Remember that when Eric and I first started releasing these plugins, the goal was not only to create small plugins that solved problems we were experiencing as bloggers, but also to do so in a way that made it as simple as possible for others to use in their day-to-day writing.

And since there are problems that he and I still experience, we continue to update the plugin.

Read More

Regarding my development environment, this is the first year that I’ve made drastic changes to my toolset in several years (once I find things I really like, I tend to stick with them).

Atom Packages for WordPress

Case in point, in the last few months alone:

And with these changes come some other necessary configuration changes. Specifically, I still use PHP CodeSniffer but, out of necessity, its setup and configuration have changed.

Read More

A few weeks ago, Pressmatic made a grand entrance into the WordPress development space with its unique positioning as a WordPress-specific development environment.

Pressmatic with WordPress Trunk

Specifically, it describes itself as such:

Pressmatic is a robust local WordPress manager. You won’t be disappointed with the ease of use, performance, and features.

I’ve been using it ever since (and talked about it in a couple of previous posts). Generally speaking, I’ve been really happy with one.

One of the features that it claims as a major benefit is:

One-click integration of Xdebug + PHPStorm.

And that’s great if you are using PHPStorm; however, those of you who’ve read this blog for any length of time within the past year or so know that I’m a fan of Codebug (which is essentially a front-end for Xdebug) and that I’ve made the switch to Atom.

So if you’re working with anything other than PHPStorm and you’re looking make use of Xdebug with Pressmatic, here’s a step-by-step guide for how to do so.

Read More