|
aditi.av
|
April 17, 2017 at 7:49 am
Hello,
After entering the details and clicking the Register button, I get ‘We are sorry but Your request failed to pass security check. Please click the back button…’. I read the similar topics posted previously and followed few steps:-
1) We are using the WP Super Cache. So I cleared the previous cache and added the event espresso slugs in the list to exclude caching for those event espresso pages.
Then I ran the registration test again for that event, but I get the same message.
2) Then I set caching mode to off and tried registering for the event. But the same message displayed as above.
3) I deactivated the WP Super cache and now I can register for the event successfully.
My question is how can I avoid getting the error message but with the WP Super cache plugin activated?
Thanks
Aditi
|
|
Lorenzo Orlando Caum
|
April 17, 2017 at 8:36 am
Hi Aditi,
Could you double-check the slugs that were excluded from WP super cache?
We provide some default slugs in our documentation here (https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/) — however, if your slugs are different, then you’ll want to use those slugs instead of what is suggested.
For example, if your default events slug was changed to courses or workshops, then you’ll use that instead of events.
If you have checked that and it still doesn’t work, then please share a link to an events page so we can share feedback.
—
Lorenzo
|
|
aditi.av
|
April 18, 2017 at 3:20 pm
Hello ,
As of now I have disabled WP Super Cache. I haven’t changed the
event slugs.
Following is the link for the event I was talking about https://www.netherlandsmarathimandal.org/carrom-tournament/.
Regards
Aditi
|
|
Tony
|
April 19, 2017 at 7:19 am
Hi Aditi,
Any pages you have the Ticket Selector shortcode on will need to be excluded from the cache.
By default Event Espresso outputs the events on /events/ and then single events on /events/{singe-event-name} which is why we recommend you exclude those paths from caching, however it looks like you’re using the ticket selector on a standard page and that page was cached.
|
|
aditi.av
|
April 20, 2017 at 3:22 am
Hello,
Yes. We are doing it the other way. We need to change it in the future. But now the cache exclusions are working.
Thanks
Aditi
|
