|
Jonathan Brooks
|
August 26, 2015 at 10:59 am
Hello,
The website in question is cacvt.org. Events page here: cacvt.org/events. Running latest version of EE4.
When I am logged in to WordPress, there are no issues. When I am logged out, I am unable to register. I receive the cookie/empty event queue error. I know this is tied to the caching by WPEngine. I have been working with WPEngine and they have disabled the applicable page caching and also enabled Heartbeat, but the error is still there. They have redirected me back to EE support for additional assistance. Please advise what the next step might be.
Thanks,
Jonathan
|
|
Tony
|
August 26, 2015 at 12:27 pm
Hi Jonathan,
Can you follow the steps here:
https://eventespresso.com/wiki/espresso-sslhttps/
To make sure your events and checkout pages are secured.
Currently your events pages are unsecured, which means that when you select the tickets and are directed to the secured checkout page, you’ll likely start a new session (which then doesn’t have tickets within that session)
|
|
Jonathan Brooks
|
August 26, 2015 at 1:16 pm
Hi Tony,
I’m using iThemes Security and have Enabled SSL per page correctly for the three critical pages. These pages appear as secure on the backend and the event registration process was working fine until making the move to EE4 and WPEngine. I see there are other URLs mentioned on your link (/events, /registration-checkout), but I’m assuming these are just the aforementioned critical pages?
I did notice I am getting an SSL verification error through whynopadlock.com:
SSL verification issue (Possibly mis-matched URL or bad intermediate cert.). Details:
ERROR: cannot verify cacvt.org’s certificate, issued by ‘/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA’: Unable to locally verify the issuer’s authority.
Could this possibly be the root of the issue?
Thanks.
|
|
Tony
|
August 26, 2015 at 1:31 pm
I’m using iThemes Security and have Enabled SSL per page correctly for the three critical pages.
That is only securing the actual pages. There are 4 critical pages that need to do secured.
However your not securing your /events/ which is where the session starts.
So you start a session via HTTP, select tickets and the ticket selector directs you to the secured checkout page.
As your now in HTTPS it starts a new session, so no tickets have been selected.
That’s why the image shows /events/ within the image, as its not a page but an archive you need to use the filters. Also anywhere that uses the ticket selector needs to be secured, for the same reason as above.
These pages appear as secure on the backend and the event registration process was working fine until making the move to EE4 and WPEngine.
Making the move to EE4 from EE3?
ERROR: cannot verify cacvt.org’s certificate, issued by ‘/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA’: Unable to locally verify the issuer’s authority.
Possibly yes, I would recommend contact WPEngine for further advice on this.
|
|
Jonathan Brooks
|
August 27, 2015 at 6:34 am
Hello,
The SSL validation error has been corrected and force SSL is correctly active on all pages and we’re still getting the cookie/empty queue error.
Any suggestions?
Thanks.
|
|
Tony
|
August 27, 2015 at 10:35 am
It looks like your /registration-checkout/ page is still being cached – http://take.ms/TTlfY
Which pages did you request WPEngine exclude from caching?
You’ll need all of the slugs mentioned within this post to be excluded from caching:
https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/
We have a guide for setting up WPEngine here:
https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/
(Very similar to the nocache exclusions)
We have a guide for WPEngine here:
https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/
Can you double check they have setup the correct exclusions please as currently it appears they have not.
|
|
Lorenzo Orlando Caum
|
August 27, 2015 at 12:00 pm
Hi Jonathan, I also wanted to share one additional recommendation as I do recall this happening recently. The slugs that are in our documentation are sample slugs from a default installation of Event Espresso 4.
If you upgraded from Event Espresso 3 then your slugs may be a little different. They would also be different if they were renamed (e.g. registration checkout was renamed to just checkout).
I’m not sure if this is happening here but I thought I’d mention it.
You can double-check the slugs for your own site by going to Event Espresso –> General Settings –> Critical Pages. Then hover over the view links to see the actual URLs.
Thanks
—
Lorenzo
|
|
Jonathan Brooks
|
August 29, 2015 at 12:06 pm
Hi Lorenzo – that was it. One EE3 slug carried over to the upgrade and hadn’t been setup for caching properly. All fixed and working now. Thank you!
|
