Practical REST API
0 likes500 views
The document discusses replacing the use of admin-ajax.php in WordPress with the REST API. Admin-ajax.php is inefficient, not cached, lacks authentication and validation infrastructure, and results in ad hoc messy code. WordPress introduced core REST API support in version 4.4, and the REST API plugin adds built-in endpoints. Examples show converting an admin-ajax.php implementation to use the REST API instead, which is recommended as it is faster, cleaner, easy to implement and migrate to compared to admin-ajax.php.
Practical REST API
- 1. Practical REST API Why admin-ajax.php should be avoided and how Aki Björklund CTO,H1 @akibjorklund
- 2. Communication between JavaScript and PHP is done with Ajax
- 3. Historically that is done in WordPress by calling /wp-admin/admin-ajax.php
- 4. Why admin-ajax.php is bad?
- 7. 3. No infrastructure like authentication, data validation, …
- 9. WordPress REST API in core from 4.4
- 10. There are no built-in endpoints yet
- 11. Unless you install the REST API plugin
- 12. In many cases no need to write any PHP to do a lot.
- 13. But what can you do just with what the core already has?
- 17. Before
- 22. After
- 27. Best practice is to implement what you just saw as a REST Controller. Currently available only with the REST API plugin.
- 28. Summary
- 29. Use the REST API instead of admin-ajax.php
- 30. It’s faster and cleaner
- 31. It’s also both easy to implement and migrate to