Instead of this ASCII mess, it should simply be: “Who’s this?” No, it should not. If you make a OPTIONS request to the /wp-json/wp/v2/pages path, you’ll see the schema which defines all the fields that exist within a Page record, like so for the post title field, via JavaScript’s fetch(): Therefore, title.rendered is meant for … Read more
I’m seeing “The response is not a valid JSON response.” on a wordpress site
register_sidebar has a bool param show_in_rest what are the repercussions of enabling it?
Filtering posts by ACF filed using WP Rest API
I made a webhook using snippet plugin, but is not working
Displaying posts from one web site to another using REST API
Preview endpoint REST API gives 403 error
Yes, the nonce is by default always being sent via the X-WP-Nonce header – see the source here and here on GitHub. wp.api.WPApiBaseModel.prototype.sync and wp.api.WPApiBaseCollection.prototype.sync can technically be extended or modified, but I would instead disable the nonce header like so, i.e. using <Collection or Model object>.endpointModel: Collection example: const Posts = new wp.api.collections.Posts(); // … Read more
even if I put in the schema ‘type’ => array(‘string’,’null’) I can’t POST a request with this field left empty, because WP always respond with rest_invalid_param and rest_invalid_email Actually, adding the ‘null’ there does not mean that any empty-ish values like ” and 0 will be allowed. It just means that an actual null value … Read more
Believe you need to be setting the status to draft, not publish https://developer.wordpress.org/rest-api/reference/posts/