Hi @danyellhubrix, sorry you’re having trouble here. That work-around is definitely not something we’d recommend.
The “Widget URL” value you have is strange, the plugin installs with 11.1:
https://github.com/auth0/wp-auth0/blob/master/lib/WP_Auth0_Options.php#L154
We actually just came out with 11.5 right around when you posted this so it’s possible that you just missed the release. Strange, though, that it was set to that. The one you mentioned before should work:
//cdn.auth0.com/js/lock/11.5/lock.min.js
… but if not, try the version right before:
//cdn.auth0.com/js/lock/11.4/lock.min.js
Let me know if that solves the problem!
I went to GitHub and manually updated the “Widget URL” field based on the most recent version available.
My problem isn’t which version is mentioned in that field, my problem is that the plugin is not including the JS regardless of the value I enter in the “Widget URL” field.
To try to get ahead of other “did you try?” style questions, I tried:
– disabling (nearly) all other plugins (except WPML as deactivating those puts our site in an unuable state)
– disabling cache, minify, compressing, defer’d load etc. (we use WP Rocket)
This is on a DEVELOPMENT server so we have wiggle-room to try things… but we need to try something that will actually help isolate/identify the problem.
I should mention that our development server has a (deliberately) non-valid SSL certificate, so https works just fine but generates browser warnings (some APIs don’t like that either)… but that should not prevent a .js file from being enqueued, should it?
Hi @danyellg, sorry for the trouble here.
Your certificate won’t affect the ability to load our JS so that’s definitely not it.
A few questions for you:
– If you search the source code for the widget URL, you don’t see it anywhere? If yes, how about the Network tab in Chrome (or similar in whatever browser you use)?
– Are you using wp-login.php, a shortcode, or a widget?
– Are you using passwordless?
If you’re able to post a link to where I can see the form in action, that would be helpful (but not required).
Thanks!
@danyellhubrix @danyellg – I haven’t heard back in a while so I’m going to mark this thread as resolved. If you’re still having issues, please post back with answers to the questions above and I’ll be happy to help.
Thread IS resolved. For posterity: this was caused by a plugin conflict with Antispam, an old and somewhat-neglected plugin.
