Book Image

Learning WordPress REST API

By : Sufyan bin Uzayr, Mathew Rooney
Book Image

Learning WordPress REST API

By: Sufyan bin Uzayr, Mathew Rooney

Overview of this book

The WordPress REST API is a recent innovation that has the potential to unlock several new opportunities for WordPress developers. It can help you integrate with technologies outside of WordPress, as well as offer great flexibility when developing themes and plugins for WordPress. As such, the REST API can make developers’ lives easier. The book begins by covering the basics of the REST API and how it can be used along with WordPress. Learn how the REST API interacts with WordPress, allowing you to copy posts and modify post metadata. Move on to get an understanding of taxonomies and user roles are in WordPress and how to use them with the WordPress REST API. Next, find out how to edit and process forms with AJAX and how to create custom routes and functions. You will create a fully-functional single page web app using a WordPress site and the REST API. Lastly, you will see how to deal with the REST API in future versions and will use it to interact it with third-party services. By the end of the book, you will be able to work with the WordPress REST API to build web applications.
Table of Contents (16 chapters)
Learning WordPress REST API
About the Authors
About the Reviewer

Backward compatibility

Backward compatibility has been one of the main tasks, ever since the release of the first version of the plugin, and the developers behind it are trying to be committed to this aim. The second version, which will be merged into the core, is not going to provide full backward compatibility, but at least the plugin will continue to exist as a backward-compatibility layer that will allow any plugin that was developed in the plugin's first version with the ability to function properly.

It is obvious that developers are not going to be recreating the plugin from scratch and would rather be porting things over from the first version to the second one.

Thus, the routes will have to be prefixed, and the core will make use of a wp prefix, and all of the custom routes will be assigned their prefixes. The wp-JSON prefix that is currently used for routes is most likely not going to be used, and instead websites that will be using the plugin are going to get the old WP-JSON routes...