|
CasMar
|
December 5, 2024 at 3:44 pm
Hello,
Some of our customers are reporting the registration issue. The error message says:
“An error has occurred: Your form data could not be applied to any valid registrations. This can sometimes happen if too much time has been taken to complete the registration process. Please return to the Event List and reselect your tickets. If the problem continues please contact the site administrator.”
Here is one of the direct links to the class:
https://cascadeconnections.org/classes/nurse-delegation-march-2025/
I tested with multiple browsers, and it usually works the first time IF I clear the browser cache before registering. If I try for the second time, it gives me the same error message, and I will have to clear the browser cache again to make it work.
The Session Lifespan is set to one hour in the registration form setting.
WordPress version: 6.7.1
Event Espresso version: 5.0.31.p
I have W3 Total Cache installed (version 2.8.0), and I recently upgraded to premium, so I am wondering if that has something to do with this issue.
Thank you very much for your time.
|
|
Tony
|
December 6, 2024 at 5:57 am
Hi there,
Can you let me know the specific steps you are taking when testing this, please?
I’m asking because I’ve just run 3 registrations back to back with no errors, so I’m wondering what I’m doing differently.
(Side note – any registrations you find under my name can be cancelled and deleted)
|
|
CasMar
|
December 9, 2024 at 11:40 am
Hi Tony,
Thank you very much for your reply. I now can’t replicate the issues. I also tested 3 registrations back to back with no errors. I tried to remember the changes I made to the website within a week, and these are the only two things changes:
1. Adding more classes.
2. Checked the checkbox for the “Eliminate render-blocking CSS by moving it to HTTP body” in the W3 Total Cache’s Minify setting.
I uncheck the “Eliminate render-blocking CSS by moving it to HTTP body” checkbox on December 5th (shortly before I posted the question on this forum), and now the class registration seem to be working. Does this make any sense?
I am not 100% sure this was the cause of the registration error. I will check the checkbox again sometime today and will see if I can replicate the issue.
|
|
Tony
|
December 9, 2024 at 5:00 pm
So generally, the error you posts would often be caused by caching… however, I wouldn’t have expected the above option to cause it (although possible).
Did you try with the option enabled again at all?
|
|
CasMar
|
December 9, 2024 at 5:38 pm
Hi Tony,
I enabled the “Eliminate render-blocking CSS by moving it to HTTP body” option again in W3 Total Cache setting, and registration went through with no problem (both single student registration and multiple students at the same time). I don’t know why it works now, but I would consider this as resolved for now.
You mentioned that this error would often be caused by caching. If this happens in the future, what should I be trying to troubleshoot? Should I be clearing both browser cache and site cache? Anything else I should be checking? We also use Cloudflare service, and I purge cache to test things regularly.
Thank you very much for your time.
|
|
Tony
|
December 10, 2024 at 1:13 pm
EE already sets a bunch of cache busting values within it to try and prevent plugins from caching its request (E-Commerce requests like EE, can’t really be cached!).
So usually caching issues are when server-side caching is forced on all pages (looking at your GoDaddy Managed WordPress hosting, although others do the same!) or from someone force caching within the plugin they are using.
The first thin I recommend doing, is excluding EE pages from caching and we have a guide on that here:
https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/#:~:text=Begin%20by%20logging%20into%20your,to%20the%20no%2Dcache%20list.
Cloudflare is a little different, that usually detects is the user has a session correctly and disabled the cache, but does it have the option to exclude specific URI’s?
|
|
CasMar
|
December 16, 2024 at 1:16 pm
Hi Tony,
Thank you for the suggestions. I checked to see which EE pages were excluded from caching, and my setting was correct. Our web hosting company is DreamHost (domain is registered through GoDaddy, but we host on DreamHost), so our setting is DreamHost VPS + W3 Total Cache + Cloudflare.
After reading your reply, I double-checked all settings for the W3 Total Cache, and when I unchecked the “Enable” Minify setting, it resolved the issue completely! This setting has not changed for a long time, so I don’t know why it started to affect our website now.
Cloudflare has the option to exclude specific URIs, but I didn’t have to do it to fix the issue.
Thank you for all your help!
|
|
CasMar
|
December 16, 2024 at 1:18 pm
I forgot to mention that we started to see the same error message again on December 10th again. And the fix was to uncheck the “Enable” Minify setting in the W3 Total Cache.
|
|
Garth
|
December 16, 2024 at 2:17 pm
That’s great. Thank you for sharing the fix was caching.
|
