sliao

I see, so it’s meant to be a more general suggestion to check whatever developer tools one may have.

I’ll close this ticket as we found a workaround by going back to the Classic Editor.

I figured out my issue in my production environment, which wasn’t related to this error. However, I’m still curious about this error, which I saw in my development environment. Does this error get returned if we started our request (getting a code to append to some url [domain A]) w/ domain A and continued the flow/testing with domain B? Is that a built-in security feature that disallows that?

I tried deactivating and reactivating the plugin and I’m still experiencing the same error that @bcgreijnlautier did. Do you have any other suggestions?

Hi Oleg,
Where are these developer tools?

• This reply was modified 3 years, 5 months ago by sliao.

I understand the problem more clearly now, but I can’t figure out how to edit my original post, so I’ll write here. The problem is that, unlike how submitting the login form as part of the typical wp-login.php page will cause the user to be redirected [to the /oauth/authorize endpoint] given the redirect_to b/c the wp-login.php is no longer available to the logged in user, submitting the login form as part of the always available homepage will not redirect the user anywhere after that page/url is refreshed.

My question remains: how does one use the WP OAuth Server plugin when the login page is the homepage?

• This reply was modified 4 years, 9 months ago by sliao.

Realized I miss the part that I was still logged in to the wordpress site itself, so the mystery’s been resolved, aka I have to make sure I’m logged out of the wordpress site too.

I had to use a random other value (e.g. ‘my app oauth’), so it works now, but my question remains.