Kerygmata

Hey @jonathandejong,

Just installed your plugin and it is working great in WordPress 4.9.1! Thanks for working on this. The current plugin here was not working in my new installation with current WordPress.

Would be great to have this in the WordPress plugins repository, but I suppose you are waiting on a response and I don’t see one yet.

Either way, thanks for getting this up to date. I’m thankful to everyone who has worked on this, because it is very useful!

• This reply was modified 6 years, 12 months ago by Kerygmata. Reason: did not read entire thread

Hmm, not sure. Seems like it should work. That’s the only place I noticed that error in the source code –so seems like something surrounding that key.

I wonder if it is something to do with your server. Looks like some special instructions for WP Engine for example.

Not sure if this would matter, but I have it working and this stuff:

RewriteEngine on
RewriteCond %{HTTP:Authorization} ^(.*)
RewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]

is right before the whole # BEGIN WordPress in my .htaccess

Good luck debugging. ??

Did you setup your secret key correctly?

It was suggested to use a string from here https://api.www.ads-software.com/secret-key/1.1/salt/

Seems like that could be related to the error, not sure though.

if (!$secret_key) {
            return new WP_Error(
                'jwt_auth_bad_config',

Well, I think most of us using JWT are likely working with things like the WordPress API and need the the JWT Tokens to authenticate specific endpoints that we don’t want left open. I don’t need a login, that is already good on our site.

Before looking closely I thought maybe that was part of your plugin since it was posted here. This won’t be what I personally need.

Thanks!

This looks cool. We already have User login via Facebook setup, but I need to be able to use the Facebook token data to make API requests for user data that we won’t want open to the public. @pablo Will this plugin work well with the WordPress API, or custom endpoints in that?

https://github.com/jwmcpeak/TutsPlus-Headless-WordPress-with-React/tree/master/4.4

@jvertucio What about when we don’t have a current user and are coming from a third party scenario interacting with this?

Nevermind. This was resolved here: https://github.com/airesvsg/acf-to-rest-api/issues/176

Settings show up when you comment out that line and just set the version in the Dashboard.

Since this is already open I’ll add my issue here. I am using WordPress 4.8.2, ACF (not Pro) Version 4.4.12, ACF to REST API Version 3.1.0.

For me the Settings are not showing up at all. Wondering if these are removed, or if it is supposed to work still in 3.1.0?

When I go to https://<mylocalhostdomain>/wp-json/acf/v3 I get a JSON response, so seems to be working fine.

I’m having the same issues, but the import of the duplicator sql file fails to bring in wp_users. I paid for a pro version of this https://www.ads-software.com/plugins/wp-migrate-db/ which is pricey but works well. Duplicator’s setup for install is faster, but I will likely just go back to my old work flow at this point.

Ok, will do –thank you.

Has this version been released Marcus? I am looking at version 2.3 in the repo.

Thanks

Ok, I’ll take a look at it on my next project. Must be a bug on my end then since on my last project it did not do this.

I was not sure if it came through an update or something, but I will assume it is something in my code for now.

Thanks

Helpful -gxdesigner thanks.

The absolute path in the css files worked great. Of course, I had to purge the crap outta all the caches and what not. At least its working now.

Thanks,