Whenever a major version of WordPress is released, WordPress.org will send a reminder to plugin authors to test their plugins with the latest version, and also to update the Tested up to value. This gives your plugin users some peace of mind that your plugin has been tested and works with the latest version of WordPress. To update this value, you don’t need to release a new version of your plugin, you can simply update the readme.txt file in your latest tagged version.
Updated: September 29 2017
In Part 1 of this series, I showed you how to start adding Customizer functionality to your theme (or plugin). As well as showing how to add Panels & Sections, I also walked through the process of creating the individual Settings and UI Controls, sanitizing your data, updating the live preview and retrieving your settings. In Part 2 we’re going to look at creating Customizer Custom Controls.
Updated: September 13 2017
If you’ve used WordPress in the last couple of years, you’re no doubt familiar with, or have at least heard of, the Customizer. The WordPress Customizer allows users to modify and configure theme options, whilst also providing them with a live-preview of those changes. The Customizer was built to provide theme developers with a standard interface they could use when providing customisation options within their theme.
One thing that’s really been annoying me lately is the number of plugins that are flooding the WordPress Dashboard with useless and annoying notifications or nags.
With the release of WordPress 4.7 this week, comes the addition of the WP REST API endpoints for posts, comments, terms, users, meta, and settings. The foundation for the WP REST API has been in core since WP 4.4, and 4.7 sees Part 2 of the REST API Content Endpoints being added.