|
jbuckle
|
February 21, 2019 at 5:12 am
I’m receiving the “Nothing in your event queue” error on all my events. I’ve confirmed the issue is present for multiple users.
I’ve already done the following:
- cleared the server-side cache
- set rules to prevent EE pages being cached
…but to no avail. What else should I be looking at?
-
This topic was modified 5 years, 8 months ago by
 jbuckle.
-
This topic was modified 4 years, 8 months ago by
 Garth.
|
|
Tony
|
February 21, 2019 at 5:36 am
Hi there,
‘Nothing in your event queue’, 99% of the time is caching.
Does it work when logged into the site but not when logged out?
Can you link me to an event I can use to test?
|
|
jbuckle
|
February 21, 2019 at 5:49 am
Hi Tony. Yes, I’ve just confirmed the problem persists when logged out (and I’ve received reports of users having the same issue).
You can try:
https://www.mwcyomo.com/bcn/en/reserva-actividad/molecular-plasticity-la-relevancia-de-las-proteinas-ductiles-q16/
|
|
Tony
|
February 21, 2019 at 6:32 am
Ok, so I know this worked previously as I’ve tested on your events before, so what has changed recently on the site/server?
You rule out a plugin conflict with the Health check plugin.
First, you install the WordPress Health Check plugin.
Then, you can rule out a plugin or theme conflict if you go to WP → Dashboard → Heath Check → Troubleshooting. There you’ll Enable Troubleshooting Mode, then once that’s activated you’ll reactivate Event Espresso only via the Health Check’s Troubleshooting item in the WP admin bar.
At that point, can you check to see if the issue persists?
|
|
jbuckle
|
February 21, 2019 at 6:46 am
I’ve just installed Health Check, entered Troubleshooting Mode, and re-enabled EE only. I then viewed an event from EE > Events > View – and got the same error.
The EE event was however using the normal site theme, despite Health Check claiming that 2016 was enabled, so I’m not sure I’ve configurated or tested this correctly.
|
|
Josh
|
February 21, 2019 at 9:49 am
Hi,
I’ve already done the following: set rules to prevent EE pages being cached
May I ask what were those rules you set? Did they include the “/es/programa/reserva-actividad/paso-2/” page? If so, then the rules are not working. So your other option may be to disable the Varnish cache for that site.
|
|
jbuckle
|
February 21, 2019 at 10:37 am
The rule is looking for URLs containing “reserva” and “venues:, which should cover all of the EE critical pages. I’ve also tried pausing the cache (and it’s still paused now), but that doesn’t make a difference.
|
|
Josh
|
February 21, 2019 at 11:21 am
The http headers show varnish caching:
https://slack-files.com/T02SY781D-FGCJXR932-8257477968
You may need to contact your host and ask them to bypass the cache for that page.
|
|
jbuckle
|
February 21, 2019 at 11:40 am
Ah, I see! Thanks for flagging that.
I was under the impression that the aforementioned rule was already preventing caching here, so I’ll flag this with my server team.
|
|
jbuckle
|
February 21, 2019 at 3:40 pm
And the response from the team is:
But the header says : X-Cache : miss which means no cache locally and Missed in the cache remotely and therefore passed through the content also expires before the content was created. all of which if they looked would say that its not being cached.
|
|
Josh
|
February 21, 2019 at 3:47 pm
If the page itself wasn’t served from the cache, then something on your server (usually related to a caching mechanism) is deleting the session transient key for the session. That’s what can lead to the “nothing in your event queue” error.
|
