horatiub

Hi.

It is def very slow. We tried it on two different sites. The site is not slow since we use dedicated servers. Basically every time we enabled the plugin, the WordPress Admin area takes about 5-6 seconds to move from one screen to another. So something is being reloaded every time you navigate from New Post to Settings for example.

Same issue here. Wish there was a way to make it work though.

Yes, I have to look into that for sure. I wonder if access to all posts opens up any security issues.

Here is what I learned by talking to a WordPress dev. Not sure if it’s something you need also

Using oAuth is a pain and making it work in your context is going to be a big pain. In fact, given the way that you’re using the API, I don’t think you should do any authentication as doing so could create unforeseen security issues.

In my article in Torque on working with meta data via the REST API, I showed how to use the filter for opening access to additional arguments. In that case it was meta_key and meta_value. You could use the same basic idea to make posts_per_page a publicly accessible argument.

You should keep in mind the dangers of doing so. You’re going to want to set a limit on the max number of posts per page to prevent third parties from making huge requests with it, which shouldn’t be too hard to do.

Article here https://torquemag.io/working-meta-data-using-json-rest-api/

Brian, if you can share the code for the basic auth plus modified key auth, would be awesome! That’s the route we will go also since we just need the app to be able to pull down all articles, and nothing more for now.

Sorry. I did manage to get the previous step going, it was an error with callback and not using http.

So I got to the point to access and using this call which I’m not sure if it’s correct

https://username:[email protected]/oauth1/authorize?oauth_token=ooz77Fe76MXWyUcOPdhfaqmG

Missing OAuth parameter oauth_verifier

So I got to the point to access.

Missing OAuth parameter oauth_verifier

Any ideas?

Just did and I’m getting the same thing when I run wp oauth1 add

p?root@server1 [var/www/]

but no output.

This is crazy! ??

I think they run the command at the root level, not in the wordpress folder. Should it be run in the index folder of the WordPress install?

Since I couldn’t figure out how wp-cli worked on the server – it’s installed but doesn’t output the keys, someone pointed me out to this

https://github.com/WP-API/OAuth1/issues/39#issuecomment-57620637

So that plugin generates the keys, but hopefully the are the same ones

Here is what I did so far, and maybe I missed a step:

Installed the WP API plugin
Installed the Oauth1 server https://github.com/WP-API/OAuth1

I had the host install wp-cli on the server

But when I run the $wp oauth1 add command, there is no output to show the key. So I used a plugin by someone in github that generates the keys with it.

Question is: do I still need the client-cli installed?

Only problem is that after this

Copy the contents of “combined call (as GET)” into “CUSTOM API CALL” (delete any existing content) and press the “Call” button

Im getting OAuth signature does not match

This is where I’ve been stuck and no idea how to fix it.

I have the same problem. Building a mobile app so not sure what to use. Setup Oauth1 but doesn’t work. Getting OAuth signature does not match

So I managed to install the Oauth server in WordPress but not sure how to run the bash command from the dedicated server. Everything errors out.

Any ideas?