Through more experimentation, I found the culprit- This does not work: curl_setopt($ch, CURLOPT_POSTFIELDS, $jsonDataEncoded); This does work: curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($data)); So it was the processing of the data in $data through curl which was causing the permission problem.
You don’t set featured image for your post ,so return 0 in feature image obj. after set it you can use featured image obj. for example: I wrote this with PHP, you can upload this to another host and display the images of the WordPress website that you specified in the URL variable on those … Read more
wp-api didn’t has any route for new user registration as the route /users requires authentication for create operation As far as I know, using proper authentication (I’m using JWT), rest API does let you create new users. The problem is that if you go that way, you have to implement your own mail-verifcation system, since … Read more
fetch returns a promise, so you want to wait until the promise is resolved. For example: new wp.api.models.Post( { id: 1 } ).fetch().then( console.log ); or doing something with the data: new wp.api.models.Post( { id: 1 } ).fetch().then( post => { console.log( post ); } ); To address your comment, Promises are async – so … Read more
It is usually easier for me to decide how the front end should behave, and then determine how to get the appropriate data. So, in your example, services would be a module with some functionality, and then service-a would be the slug. However, if you only care about the URL looking the same you can … Read more
They have modified this filter in the latest 2.0 Beta 14.0 release. The behavior with the value -1 you’re familiar with was in fact a bug. You should define new parameters in your request. This link should be interesting: https://github.com/WP-API/WP-API/issues/2357
Just to make sure: You have a local environment, without WooCommerce, from which you want to create a product in your WooCommerce WordPress site, and make sure that the images you provide are uploaded to your WordPress site. 1. Install library Make sure that you in your local environment have installed the WooCommerce REST API … Read more
I was facing a similar issue when trying to use Client-CLI with OAuth 1.0a plugin, however I found a solution here on the official repository. In the file lib/class-wp-json-authentication-oauth1.php on line 524, change the following code: $base_request_uri = rawurlencode( get_home_url( null, parse_url( $_SERVER[‘REQUEST_URI’], PHP_URL_PATH ), ‘http’ ) ); to: $home_url_path = parse_url(get_home_url (null,”,’http’), PHP_URL_PATH ); … Read more
The issue was my staging and dev were using one minor version difference of the WP API plugin which Im assuming made a destructive change.
No Result found(404) because your plugins endpoints may not have been compatible with the WP Rest API v2. Please see the list if they are compatible or not : http://v2.wp-api.org/guide/plugins/