I first released Scheduled Post Shortcut for WordPress almost two years ago (officially, it’ll be two years ago this June but who’s counting, right? 🙂).

It’s one of those really simple plugins that works well for those who schedule content far out and want to easily see how many posts are in their backlog, but not much else.

Scheduled Post Shortcut 1.5.0

In short, it’s a plugin designed for people who blog regularly and frequently.

Anyway, I had a notice on the project page in the WordPress Plugin Repository that the plugin had not been tested against the lastest version of WordPress.

So while making sure it was compatible against WordPress 4.9.4, I also brought it up to date with some other standards.

Scheduled Post Short 1.5.0

For those who are interested in the details, they are quite simple. First, note that the purpose of the plugin hasn’t changed at all.

The Short Of It

Simply put:

The plugin introduces a new Scheduled menu item under the Posts menu that will take you directly to the Scheduled Posts page so that you can manage your content.

If you’ve installed it via the WordPress Plugin Repository, then you will see an update in your Plugins dashboard to update to the latest version.

The Technical Details

For those who are curious about the technical details of what went into the release, check out some of the notes below:

  • Ensured support against WordPress 4.9.4
  • Add support for Namespaces
  • Changed the coding standards to PSR2
  • Bumped the version number to 1.5.0
  • Updated Composer information to provide updated URLs

For those who are astute in reading through some of the details, you’ll see that I’ve briefly mentioned Blogging Plugins in the Composer file.

Furthermore, there is still work that I want to introduce in the next version that uses Yarn for managing and JavaScript, nothing changed for how those particular features work for this particular release.

Finally, the version of this plugin on GitHub is not currently in sync with what’s in Subversion for WordPress. I’m still trying to determine how to best handle that (and if I want to continue to keep the two repositories in sync).

Most likely, I will.

Regardless, if you’re looking for the latest version, you’ll find it here. And if you enjoy using it, please don’t hesitate to share it or give it a rating in the repository.