|
Praxis
|
September 18, 2020 at 1:35 pm
Hi there,
I’m experiencing a new bug since the latest Yoast update (14.9). I’ve asked Yoast for support, but I was hoping you folks might also be able to help me narrow down the specific conflict, as they are unlikely to be familiar with EE.
With the WP Users integration addon (2.0.17.p) activated, customers are forced to login or create an account before registering for an event. Now, when they get to the login or the register screen and try to login with accurate credentials, they get this error message:
“The requested route wpuser_login could not be mapped to any registered modules” and if you try to login again, the error message adds “: You must consent to these terms in order to register” to the end of the previous message.
e.g. https://snipboard.io/5cC2EP.jpg
The user does actually get logged in, but they are not redirected back to checkout and there is no indication that they are logged in.
Sometimes the error does not appear, but the page gets stuck with a spinning gear icon.
This doesn’t happen while logging in to the site via the standard WP login page.
No relevant errors appear in the js console.
When I deactivate Yoast, there is no problem.
Any ideas?
|
|
Tony
|
September 22, 2020 at 7:40 am
Hi there,
I’m pretty sure this is something Yoast should fix as they are currently hooking into every ajax request and adding a ‘fill_cache’ callback to it which in short pulls posts on your site to create a cache, none of which is needed on the EE ajax request sent to log in.
I recommend creating a ticket for them to investigate this further as it may also cause issues with other plugins.
For now you can use something like this:
https://gist.github.com/Pebblo/ada38c7a10b6839fff20d4bf9b0e67ac
Which removes the above callback on that specific request.
You can add that function to a custom functions plugin and we have some documentation on creating one here:
https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/
|
|
Praxis
|
October 8, 2020 at 4:58 pm
Thanks so much, Tony. Your workaround does the trick. And thanks for explaining what’s happening. I’ll pass it on to Yoast.
|
