Ran into this same issue and I found the answer after many hours and almost giving up. It’s in a bit of code that written to make the Customizer work with playlists. Checkout this comment from /wp-includes/widgets/class-wp-widget-text.php: /** * Enqueue preview scripts. * * These scripts normally are enqueued just-in-time when a playlist shortcode is … Read more
Use below code snippet function video_get_post_meta($object, $field_name, $request) { return array( ‘video’ => array( ‘length’ => get_post_meta($object[‘id’], ‘length’, true), ‘file_name’ => get_post_meta($object[‘id’], ‘file_name’, true), ‘thumbnail_’ => get_post_meta($object[‘id’], ‘thumbnail_’, true), ‘video_url’ => get_post_meta($object[‘id’], ‘video_url’, true), )); } add_action(‘rest_api_init’, function() { register_rest_field(‘post’, ‘video’, array( ‘get_callback’ => ‘video_get_post_meta’, ‘update_callback’ => ‘video_update_post_meta’, ‘schema’ => null ) ); } Output … Read more
You can get it easily by making a GET request to: http://yourdomain.com/wp-json/. You will see your site name, description, url and home…
I’m guessing you haven’t exposed meta_key and meta_value to the REST API with the rest_query_vars filter, so this should do it: function my_add_meta_vars ($current_vars) { $current_vars = array_merge ($current_vars, array (‘meta_key’, ‘meta_value’)); return $current_vars; } add_filter (‘rest_query_vars’, ‘my_add_meta_vars’); Then you can refer to meta_key and meta_value in your query. Be aware that this obviously exposes … Read more
On the “REST API” tab, you should be to enable the new post type to show all the custom fields in the standard WordPress REST API. Also, in each field’s options, you should be able to set if that field should be viewable and/or editable via the API, if you only want to show a … Read more
It’s not so difficult. All you have to do is to add a condition and check if the book_id param is passed. You can even check if this param is correct (for example if the book_id should be a number, then you can check if it is): add_filter( ‘rest_gallery_query’, function( $args ) { if ( … Read more
Solved by this lines: RewriteEngine On RewriteBase / RewriteRule ^wp-json/(.*) /?rest_route=/$1 [L]
If you wish to do it this way, you need to use the <ServerSideRender /> component in your edit method. Here’s a basic implementation, based on the PHP block registration code you provided. import { ServerSideRender } from ‘@wordpress/components’; registerBlockType( ‘some/block’, { title: ‘Some block’, attributes: { stuff : { } }, edit( { className, … Read more
You can use the filter hook ‘rest_index’ : add_filter(‘rest_index’, function ($response) { $data = $response->get_data(); $data[‘namespaces’] = []; $data[‘routes’] = []; return $data; }, 9999, 1); It is possible to remove your route from $data[‘namespaces’] and $data[‘routes’]
Answering my own question. For plugin developers, the directive is to use current_user_can() in your code as usual in the REST endpoints, as Core does. WordPress 5.4 does not support authenticated requests originated from outside WordPress to the REST API yet. But your clients can use plugins such as Basic Auth, OAuth2 or JWT to … Read more