I’ve written plenty about item-oriented PHP and the WordPress REST API for Torque over the past few years. I’ve additionally touched on the usage of Composer for dependency management and to offer an autoloader, as well as covered unit testing. The primary message of the whole thing I’ve written is that through using the set up best practices of software improvement to how we expand for WordPress, we can create higher plugins.
This is the primary of articles to pull together those standards in a practical, functional example. I’ll be on foot through growing a WordPress plugin to regulate the competencies of WordPress REST API endpoints so that they may be better optimized for search. The plugin is available on GitHub. You might also want to browse the commit log to see how I put it together.
In this series, I’ll cowl structuring plugins and training the usage of contemporary object-oriented PHP and not only the way to make it testable, however additionally a way to write computerized assessments for it. I will cowl the distinction between unit tests, integration assessments, and attractiveness checks and show you how to write and automate going for walks each kind. This article begins the series by showing how to use filters to alter the WordPress REST API’s usage of an object-orientated technique.
Improving WordPress Search Using the REST API
Plugins like SearchWP or Relevansi, or integrations with ElasticSearch — a technology that uses a particular stack than WordPress — using Jetpack or ElasticPress, are frequently used to enhance WordPress seek. These plugins provide higher seek effects and often pair nicely with a faceted-search interface that’s exquisite for eCommerce apps.
Search via the WordPress REST API inherits all of those equal troubles and the same solution. In this post, I will begin by searching at how search works via default and what the constraints are. Then we’ll look at how to regulate the hunt using specific methods and combine them with SearchWP.
WordPress’s built-in seek capabilities frequently need to be progressed the use of doors offerings. While this newsletter is about an object-oriented method to modifying how WordPress REST API routes for posts paintings, the realistic instance could be enhancing search.
When WordPress is used because the again give up for a decoupled front stop together with a local mobile app or net app, probable constructed the usage of Vue or React or Angular, having satisfactory search via the REST API is essential. The code this newsletter covers will assist you if your app’s customers need to discover the proper product variation or seek content with the aid of a complicated set of rules based on multiple taxonomies, and al. Also,writing custom code, no longer simply putting in a plugin.
Searching Posts with the WordPress REST API
If you wanted to search for all posts that had been of the put-up type “product” on a site, the usage of the search terms “Taco Shirts” you would request the /wp/v2/product?S=Taco+Shirt endpoint. If you wanted to improve the pleasantness of the outcomes, the answers I indexed above would help.
As we mentioned above, WP_Query, the put-up endpoints of the WordPress REST API use, is not a tremendous tool for search. More specially, WP_Query, possibly due to its dependence on MySQL, is not as good as specialized search equipment that has a tendency to be built by the use of NoSQL databases.