|
2silda
|
October 9, 2024 at 1:40 am
We have a problem on our site with registration. Customer selects the event from list, selects 1 ticket it writes in opened pop-up that ticket was successfully added for this event and when he clicks on “Proceed to Registration” it writes “Nothing in your Event Queue” and “You need to Return to Events list and select at least one event before you can proceed with the registration process.”
So customer gets back, and adds the event ticket one more time, now everything works.
So here are things that’s strange:
1. It happens only to one event, which ticket is free. Other events reigstration works fine.
2. If customer clicks after selecting ticket to “Cart” button it works, but doesn’t work if clicking “Proceed to Registration” as mentioned before.
3. If you go back and add this ticket again, everything works.
I tried to empty and disable cache completely, but it didn’t do the trick. Everything has been working nicely for the past 5 years, so there might be some bug somewhere.
|
|
Tony
|
October 9, 2024 at 6:05 am
Hi there,
Can you add a link to the specific event this is happening on, please?
Issues like these are almost always related to caching but I’ll check the request headers once I know where I need to look and let you know from there.
|
|
2silda
|
October 9, 2024 at 6:19 am
This reply has been marked as private.
|
|
Tony
|
October 9, 2024 at 6:42 am
Hmm, strange.
I’m not getting any errors.
I’ve tested registrations on multiple browsers but each time the registration step works as expected.
Are you able to reproduce this on your end?
|
|
2silda
|
October 9, 2024 at 6:46 am
That is very strange, but yes I can confirm it is working right now. It didn’t work for day or so. I didn’t make any changes also. Hope it will stay like this – I should had screen-record the issue.
|
|
Tony
|
October 9, 2024 at 7:33 am
I’ve seen the issue you are describing before so a video wouldn’t help, need to see the request/response headers when it’s happening.
99.9% of the time, it happens when the server is serving cached content, be it page or object cache. The other .1% is session based issues causing thise, I think I’ve seen 1 or maybe 2 in EE’s lifetime with that happening.
If it comes up again, let me know and I’ll jump into the above event to test.
|
