Properly process a custom WP REST API request (Authenticate, Authorize + Validate)?
I have a custom WordPress REST API endpoint that returns the output of get_template_part Note that the REST API expects your endpoint callback to always return the response (e.g. the template part output in your case), and not echo it or anything else. And after the callback is called, the REST API will send some … Read more
The core WordPress data structures and the REST API’s core controllers aren’t really designed to ever treat post content as anything other than one big string. As Tom mentions in the comments, this means that storing JSON in that field will result in it being presented as an escaped string in REST responses rather than … Read more
The answer for me was setting the X-WP-Nonce with the wpApiSettings.nonce in the headers.
I found the issue. I am missing the trailing “/” on the uri. If I add that to the individual post uri, it works as designed.
getMenu() fetches data from the GET /wp/v2/menus/<id> endpoint, whereas getMenuItem() fetches data from the GET /wp/v2/menu-items/<id> endpoint, but they have the same usage syntax, where you just need to pass the ID of a menu or menu item. As for getMenuItems() and another function you can use — getMenus(), the endpoints are GET /wp/v2/menu-items (for … Read more
Resolved! If no feature image exists, then _embedded[‘wp:featuredmedia’] is not used. To resolve, the prop value needs to be wrapped into a conditional. <Post key={post?.id} id={post?.id} title = {post?.title.rendered} link = {post?.link} img = {post && post._embedded && post._embedded[‘wp:featuredmedia’] ? post._embedded[‘wp:featuredmedia’][0].source_url : ‘ ‘ } category = {post?.categories} />
That’s not how post type and taxonomy registration work, they are already dynamic. You must call register_post_type on every request, no exceptions, and never later than the init hook. If you do not do this, then the CPT doesn’t exist. register_post_type and register_taxonomy store their data in PHP variables, and do not save that data … Read more
This is related to how you declare the parameter types for the endpoint. If you use integer then the parameters will be converted to integers, so in cases where a null value is being used you will get 0. The solution is to add support for both integer and null e.g. ‘type’ => [‘integer’, ‘null’],
I wasn’t sure from the Laravel docs exactly how it works there, but there are a couple of security plugins (at least) that have rate limiting on a per-IP basis: ShieldPRO WordFence This may be more useful, however, as it is focused only on rate limiting and isn’t a product, and would be more flexible … Read more