Josh C

Thanks for the clarification. You mentioned the setup not working here as well so I wasn’t sure if they were related. I saw your post there and will respond when I’ve taken a closer look.

A few questions here to help me investigate:

• Can you confirm that you’re on the latest Auth0 version, 3.5.1?
• Did you change any settings from the default? Want to make sure my configuration matches yours when I’m testing.
• Did the setup wizard finish correctly? Expected behavior is documented here: https://auth0.com/docs/cms/wordpress/installation
• Can you confirm that your Client and Connection look how it’s documented here? You shouldn’t have to do anything manually if the setup wizard completed:
  https://auth0.com/docs/cms/wordpress/configuration
• Can you copy/paste any relevant error message from wp-admin > Auth0 > Error Log and Auth0? For the one in wp-admin, make sure to include the section, please.
• Are you getting any error messages on the form when you try? Or an error screen on your site with more information?

Thank you!

• This reply was modified 8 years, 4 months ago by Josh C.

@deafjoe,

Sorry you’re having trouble getting this setup. I addressed your other questions in the 3 other forum posts and will here as well.

1) It looks like your site name has characters we can’t use in the Client we’re trying to create on the app side. I’ll make a note to look into that, see if we can come up with a better experience there.

2) The error that you’re seeing is likely because you have WP_DEBUG on, which you definitely don’t want on a production site. I created an issue on Github to handle that as it should be fixed regardless.

3) You didn’t really give us a lot to go on here and it looked like maybe it was corrected when you did a manual setup? Happy to help troubleshoot but not sure where to start. The last update would not have affected the setup, it was released to help legacy clients upgrade.

4) Delete gets rid of the settings option, which is the one that will reset for a new install. I see that the error log persists, I’ll make sure that gets handled.

We do quite a bit of testing before these releases come out, including setup, logging in, signing up, etc. We can’t ensure that every site and every configuration will work but we do put in a lot of time to try and cover all of our bases.

If you would, let’s keep the troubleshooting going in the relevant threads, if possible. I left 2 open, if it’s a single issue, let’s close one and work in the other.

Thank you

Is your other thread related to this?

https://ww.wp.xz.cn/support/topic/auth0-setup-wizard-fails/

If you would, let’s keep to a single thread. I’ll switch to that other one since it’s got a little more information.

We have not tested against that specific plugin or host, no.

If you have a login redirect, maybe try adding a URL parameter on there, like:

http://yourdomain.com/login-success?loggedin=1

That might break the cache and serve up a logged-in user page. In your caching plugin, there should be a setting covering URL parameters like that, either specific ones or all.

You also might have caching setup on your host that is not playing well with this change of state.

In the meantime, I’ll make a note to see if I can reproduce on my end.

@hasantar – Latest release (3.5.0) is live as of about an hour ago. Give that a try and let me know if you have any other issues.

If you see a red banner after updating, there will be instructions for completing the update in your Auth0 dashboard. Easiest thing to do is to create a new API token and save it under wp-admin > Auth0 > Settings > Basic > API token:

https://auth0.com/docs/api/management/v2/tokens#get-a-token-manually

You can also go to your Auth0 Dashboard > APIs > Auth0 Management API > Non-Interactive Clients tab and authorize the WordPress client you’re using.

@nilesht – Apologies for the delay, we were working on the latest release, which is live now. Give that upgrade a shot and let us know if that corrects the issue.

If you see a red banner after updating, there will be instructions for completing the update in your Auth0 dashboard. Easiest thing to do is to create a new API token and save it under wp-admin > Auth0 > Settings > Basic > API token:

https://auth0.com/docs/api/management/v2/tokens#get-a-token-manually

You can also go to your Auth0 Dashboard > APIs > Auth0 Management API > Non-Interactive Clients tab and authorize the WordPress client you’re using.

Hope that helps!

@saikatshankhari – Sorry for the delayed response. You can always generate a new token using the steps here:

https://auth0.com/docs/api/management/v2/tokens#get-a-token-manually

In the latest release (just a few minutes ago), how the plugin accesses the Auth0 API changed to not require that token so, if you’re still having issues, try the upgrade.

Thanks!