I am looking at a custom taxonomy endpoint and there are custom post types for this taxonomy but they don’t show in the endpoint. Is there something I need to add to this endpoint or something to the registering of the custom post type/taxonomy?
I have a WordPress site, and I have another server.
I am implementing the REST API with fetch() promises as requests on a Password protected page with a custom table without using a plugin (only using the WP REST API that has been merged into WordPress core – thumbs up 👍 WordPress team, that was a smart move, thank you).
I’m trying to get a custom rest api working to handle some stuff. One part I need to do requires a Post/Put to the API.
I am building and android app using react native for my WordPress blog.
I added a rest field into a custom post type endpoint as following:
We have a WordPress instance that we query through it’s API. Contents are posts, or episodes from a Podlove plug-in. We have four podcasts, though at the moment only one is set up in Podlove. We indicate the podcast an episode belongs to by adding a category. Now we’d like to add a logo to … Read more
WP 5.8 (not released yet) will include support for transforming legacy widgets into blocks. I have a custom legacy widget I’m trying to add support for transforming it into a block. Reading the docs I added the following code to one of my blocks. My legacy widget had two attributes (attribute1 and attribute2):
I can pass a single tag slug to WP REST API. But, cannot pass multiple tags slug. It gives an error – the request was made to wp-json/w1/unica/posts/unica-12-1&interact and the error message is:
WordPress Site A has an API, which is being used by another system/application (B). B is struggling to handle/controle/sanitize the posts being sent to the API, and often cause creation of duplicates. B is really struggling to solve this in their end, so I was wondering if I can add a validation-method to the endpoint in my end.
