Babak Fakhamzadeh

Thanks!

The plugin author is not planning to add this to the free version. The pro version will get something that could provide for this.
To make this work yourself…

Add something like this to your functions.php;

function wpse_modify_taxonomy() {
    // get the arguments of the already-registered taxonomy
    $language_args = get_taxonomy( 'language' ); // returns an object

    // make changes to the args
    // in this example there are three changes
    // again, note that it's an object
    $language_args->show_in_rest = true;

    // re-register the taxonomy
    register_taxonomy( 'language', 'post', (array) $language_args );
}
// hook it up to 11 so that it overrides the original register_taxonomy function
add_action( 'init', 'wpse_modify_taxonomy', 11 );

Thanks. This does not seem to be working, though. At least not out-of-the-box. The endpoint

http://mysite.com/wp-json/wp/v2/taxonomies

only returns the two default taxonomies, “category” and “post_tag”.

Explicitly asking for the “language” taxonomy like so:

http://mysite.com/wp-json/wp/v2/taxonomies/language

returns a “Sorry, you are not allowed to do that.”

In addition, the posts endpoint only seems to allow for matching posts on category or tag:

https://developer.wordpress.org/rest-api/reference/posts/

I suppose it’s possible to create a custom route which queries posts based on their language. The overview for this would be here:

https://developer.wordpress.org/rest-api/extending-the-rest-api/adding-custom-endpoints/

However, this hardly could be called ‘easy’ and requires customisation of the WordPress installation. :/

Am I missing something obvious in relation to the REST API?

• This reply was modified 9 years, 1 month ago by Babak Fakhamzadeh.

Thanks. Looking good.