|
activateyrlife
|
March 27, 2018 at 8:12 pm
It seems this problem is a common one, as I just read about 50 support threads about this. Events are working for logged in users only, otherwise we got the “Nothing in your Event Queue” message.
-I already deactivated my only caching plugin, W3 Total Cache (but I don’t have any caching enabled on it, I only use it for CDN settings).
-I asked my webhost (Pair Networks) to exclude EE critical pages (on my site, /event-registrations, /transactions, /thank-you & /registration-cancelled) from the Varnish caching plugin. It actually worked later that day that but a few days later we got reports that it wasn’t working anymore and its not working now.
-I tried deactivating all plugins except EE and that didn’t help.
-Is using a CDN a problem?
|
|
Tony
|
March 28, 2018 at 3:32 am
Hi there,
It seems this problem is a common one, as I just read about 50 support threads about this.
Of course, because it’s usually (99% of the time) caused by caching, seeing how many hosts now force caching on all pages and completely ignore no-cache headers set by plugins (such as EE) the end user gets a ‘Nothing in your event queue’ error, as they are seeing cached results 🙂
Events are working for logged in users only, otherwise we got the “Nothing in your Event Queue” message.
The fact that it works for logged in users only, points to caching, as caching is usually disabled for logged in users.
-I asked my webhost (Pair Networks) to exclude EE critical pages (on my site, /event-registrations, /transactions, /thank-you & /registration-cancelled) from the Varnish caching plugin.
There is no /event-registrations page on your site, I’m guessing you meant /event-registration/ but has the correct page been excluded? Looks like it’s still caching to me – http://take.ms/H2mnn
You need the pages that have the ticket selector shown on them to be excluded, so that means /modify-2019-weekend-away/ needs excluding.
Looks like you’ve changed your /events/ slug to be /weekend-away/ so that needs to be excluded.
It actually worked later that day that but a few days later we got reports that it wasn’t working anymore and its not working now.
Sounds like they either purged the cache and now its rebuilt, or the exclusion rules have been re-written/lost.
I’d recommend contacting your host and have them make sure all of the pages listed in Event Espresso -> General Settings -> Critical pages have been excluded permanently from server-side caching (also note the other pages I mentioned above).
-Is using a CDN a problem?
Not usually no.
-
This reply was modified 6 years, 8 months ago by
 Tony. Reason: Typo
|
|
activateyrlife
|
March 28, 2018 at 7:25 pm
Thank you, this extra information is really helpful, I will follow up my host- I figured it was something on their end but couldn’t figure out what else to ask them to do.
|
|
Tony
|
March 29, 2018 at 3:17 am
You’re most welcome.
Please do let us know how you get on.
|
|
CanvasRoadShow
|
March 29, 2018 at 7:36 am
I was told to go to godaddy to remove caching…they responded: The built-in caching plugin that comes with Managed WordPress sites is meant for “cleaning” the system cache of the site (it does not cache any activity on the site).
SO NOW WHAT? I am losing money….my (hack) web designer quit, I believe, because she didn’t know how to fix this…and has refunded me….please advise asap!
|
|
Josh
|
March 29, 2018 at 7:45 am
Hi there,
Regardless of what the support tech claimed, the cache cleaning plugin added by GoDaddy Managed hosting does cause the Nothing in your Event Queue error, and it can be disabled. You may need to ask them to escalate the support ticket and if they cannot, we have a list of recommended hosts who will be more than happy to help you migrate to a compatible hosting plan:
https://eventespresso.com/requirements/
|
|
activateyrlife
|
March 29, 2018 at 9:00 am
Hi again,
My webhost says that all the critical EE pages are excluded now from the caching. But I just tried booking the event and I still am getting the error. I tried to determine if the page is still cached (like your earlier screenshot, using inspect in Chrome) but I couldn’t figure it out, can you check again and let me know? I really appreciate the assistance!
|
|
Josh
|
March 29, 2018 at 9:24 am
They may no longer be caching those pages, but there’s still something happening that’s not allowing the session to maintain state. We’ve seen this before where the server has object caching or similar and the garbage collection was clearing the session transients.
Can you contact your host and ask them if there’s a way they can allow the session to maintain state from one request to the next?
In a nutshell, what’s happening there is you select the ticket quantity, then click the Register Now button it correctly redirects to the registration checkout page, but the session data is not longer present so it shows the error. Minor technical point: The session data itself doesn’t contain the ticket selections, it acts like a key so the registration page can look up that information. It can’t look up that information if there is no key.
|
|
activateyrlife
|
March 29, 2018 at 11:25 am
Thanks for your reply. I copied your message and sent it to my web host, his response:
It sounds like the cookie data is being stripped out. If you can
tell us what the cookie names you (the plugin) are using for session data,
we can have our admins configure Varnish to let the cookie data through.
|
|
Josh
|
March 29, 2018 at 11:42 am
Event Espresso doesn’t actually store data within cookies, but the same PHPSESSID needs to be present on each request within the session. It looks like the server is setting a new PHPSESSID with every request.
|
|
activateyrlife
|
March 30, 2018 at 7:17 pm
My host says the above change has been made, unfortunately its still not working. I’m asking them to double-check all the caching settings, anything else I can ask them to do specifically? We are getting so many emails from people who would like to book but can’t 🙁
|
|
Josh
|
April 2, 2018 at 8:28 am
Hi Erica,
We’ve received your request for priority support. We can troubleshoot at the WordPress level, but if find the issue isn’t happening at the WordPress level then the next step may be to ask the host to disable all caching (including varnish).
We’ll let you know what we find.
|
