|
SonyaJ1975
|
February 1, 2024 at 10:51 am
If I’m logged in to WordPress as admin the registration for events works fine. However, when not logged in I get a “This registration step could not be completed” message on submitting the first step of the reg form (after ticket selection).
This appeared to be working fine until yesterday. I disabled all the caching on the server and in WordPress but still the same problem. I enabled debugging in WP but that didn’t seem to show anything.
Any idea what could be going on here?
site: https://edgeoffroad.events/events-2024/
EE: 5.0.16p
PHP: 8.1.27
Web Host: WPX via Cloudflare
|
|
Tony
|
February 1, 2024 at 11:39 am
Hi there,
That error usually means there is a fatal error being thrown which should be save in the server’s error logs.
Can you check the logs around the time of a registration and see if there are any errors from Event Espresso? (Your host will usually have a section to view errors in your control panel).
Or, if you add this to your site’s wp-config.php file:
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
It will save any errors to /wp-content/debug.log and if you let me know that’s been added I can test a registration and check for errors that way.
|
|
SonyaJ1975
|
February 1, 2024 at 12:01 pm
okay, debug is enabled.
I quickly tried a registration but nothing appears to be getting logged to debug.log
|
|
Tony
|
February 1, 2024 at 12:09 pm
Hmmm, just to confirm you added it above the line that has:
/* That's all, stop editing! Happy publishing. */
Usually I advise using that snippet to replace the single line:
define( 'WP_DEBUG', false );
Like this:
https://monosnap.com/file/FixAatxjfnnxFTgWWMlsQpHr2Gq0Mr
|
|
SonyaJ1975
|
February 1, 2024 at 1:31 pm
Yep, that’s what and where I have it in place – as the snippet provided
|
|
Tony
|
February 1, 2024 at 1:55 pm
The Ajax request the checkout page uses is returning blank:
https://monosnap.com/file/rQe9LaSnupT1CSSc5Q8ZBI7sZzLrUZ
Thats not expected and with you saying it is only happening when logged out I’m guessing caching (I’m aware you’ve mentioned you’ve disabled all caching).
Have you made any changes on the site recently? Updates? New plugins? Hosting changes? Anything at all between when it worked and now.
|
|
SonyaJ1975
|
February 1, 2024 at 2:16 pm
That’s the thing – nothing has changed on the site – there was a WP auto update to 6.4.3, but I rolled that back to 6.4.2 in case that had anything to do with it.
I don’t know if our hosting provider has made any changes (it’s WPX who I think use Litespeed baked into the platform) – I’ll ask them if anything has changed.
|
|
SonyaJ1975
|
February 1, 2024 at 2:41 pm
I’ve checked with the hosting company (WPX) and they tell me nothing has changed on the server/hosting configuration.
Any ideas?
We do have full back-ups so I guess rolling back might be an option
|
|
SonyaJ1975
|
February 2, 2024 at 2:21 am
We rolled back the full site install to a previously known good point (previously we only rolled back the WordPress core – 1 version).
This appears to have resolved the issue – I’m guessing something possibly messed up with the WordPress auto-update, that couldn’t be resolved by only rolling back the core. We updated WordPress after the restore to 6.4.3 and everything still works as expected.
Thanks for your help with this
|
|
Tony
|
February 2, 2024 at 2:41 am
Hmmm, that’s a head-scratcher.
First post of a new day and already I’m lost as to why that would happen!
I’m glad its now working for you, but I don’t like ‘magic’ fixes like this as we don’t know what caused it, very odd!
|
