On the initial issues, are you positive the plugin is registering the fields to be made available to the api? the register_meta needs show_in_rest => true assigned. Also, the CPT needs custom-fields in its supports array, ‘supports’ => array(‘title’,’editor’,’thumbnail’,’custom-fields’) for that to made available when accessing the CPTs api endpoint. I cover that (with links, … Read more
Try This First: Your Problem Might Be DNS In my testing this is a problem with DNS resolving. In my case it’s because the DNS filter/cache I run on my local network wasn’t responding to requests. After restarting the service on the DNS server my requests got through quickly & easily. I would suggest checking … Read more
It looks like you’re missing the nonce part, as explained in the Authentication chapter, in the REST API Handbook: Cookie authentication is the basic authentication method included with WordPress. When you log in to your dashboard, this sets up the cookies correctly for you, so plugin and theme developers need only to have a logged-in … Read more
You can modifiy REST API responses in themes functions.php like this. function ws_register_images_field() { register_rest_field( ‘post’, ‘images’, array( ‘get_callback’ => ‘ws_get_images_urls’, ‘update_callback’ => null, ‘schema’ => null, ) ); } add_action( ‘rest_api_init’, ‘ws_register_images_field’ ); function ws_get_images_urls( $object, $field_name, $request ) { $medium = wp_get_attachment_image_src( get_post_thumbnail_id( $object->id ), ‘medium’ ); $medium_url = $medium[‘0’]; $large = wp_get_attachment_image_src( … Read more
The issue was because I wasn’t generating and sending a nonce value with the request. In order to generate a nonce value. Localize the value of a wp_create_nonce(‘wp_rest’) function call. wp_localize_script(‘application’, ‘api’, array( ‘root’ => esc_url_raw(rest_url()), ‘nonce’ => wp_create_nonce(‘wp_rest’) )); This will then be accessible to the window object of the browser which can be … Read more
It looks like you are trying to send a POST request to the /istermactive endpoint, is that correct? (I think you may want to remove the trailing slash from the endpoint?) I’m not really sure the wp-api client is the right tool for a standard ajax POST, you may want to use jQuery.ajax or use … Read more
Each of these have their own advantages and disadvantages. You might need to choose one over another, based on your needs. They are both well secured, otherwise they wouldn’t exist in the core. REST-API, The modern and well known API The REST API was added to ( or better say, combined with ) the core … Read more
The first parameter passed to register_meta() is always post for posts, Pages (post type of page) and custom post types. However, the REST API Handbook says that: Prior WordPress 4.9.8, meta fields set to show_in_rest using register_meta are registered for all objects of a given type. If one custom post type shows a meta field, … Read more
We could implement our own endpoint: https://example.tld/wpse/v1/frontpage Here’s a simple demo (PHP 5.4+): <?php /** * Plugin Name: WPSE – Static Frontpage Rest Endpoint */ namespace WPSE\RestAPI\Frontpage; \add_action( ‘rest_api_init’, function() { \register_rest_route( ‘wpse/v1’, ‘/frontpage/’, [ ‘methods’ => ‘GET’, ‘callback’ => __NAMESPACE__.’\rest_results’ ] ); } ); function rest_results( $request ) { // Get the ID of … Read more
It is not clear in the documentation, but you need to include the “_links” and “_embedded” as fields to be returned. In addition, I include the _embed parameter, as it does not require a value. As of WordPress 5.4, the resources to embed can be limited by passing a list of link relation names to … Read more