|
Delray Wannemcher
|
March 3, 2014 at 7:30 am
Hi,
My site is hosted with WP Engine. I installed and configured the plugin on the staging site. And everything seemed to be working fine. When I copied staging to production, the registration forms where producing the following error:
We’re sorry but your request failed to pass a security check.
Please click the back button on your browser and try again.
TCKSLC-DTCKSLC-PROTICSEL-227
What could be causing this specific to it being on a production site when it was working well on staging? Does it have to do with the license key?
It seems that the register now button on the single page ticket select is not directing to /registration-checkout/?ee=_register as it is on staging, but instead to /events/event-name/?ee=process_ticket_selections on production.
Any ideas on how I can solve this?
Thanks
////////////
WP 3.8
EE4 – updated to newest version on March 2nd
URL: https://www.fsxinterlinked.com/register-now/presenting-company-registration/
|
|
Delray Wannemcher
|
March 3, 2014 at 2:25 pm
Hi,
Any ideas on how we can solve the problem?
After reading other forum posts with similar problems, I was led to believe it was a caching problem. But I have since had WP Engine disable caching on core Critical Event Espresso pages/directories. Also, all critical pages have SSL and payment is processed with Authorize.net.
|
|
Garth
|
March 3, 2014 at 2:33 pm
Hi Delray,
How are you today?
WPEngine doesn’t cache on staging but they do cache production. So, after disabling the caching can you deactivate and then re-activate Event Espresso? We think the urls for your critical pages were incorrect when you copied your site from production to live.
Let us know.
|
|
Josh
|
March 3, 2014 at 2:47 pm
Hi Delray,
It looks like it works if the tickets get selected from this page:
http://www.fsxinterlinked.com/events/
Another thing to check on with WP Engine support is whether or not they’re allowing the WP HTTPS plugin. They may have a different recommendation on how to secure pages.
|
|
Delray Wannemcher
|
March 3, 2014 at 2:49 pm
I also tested from http://www.fsxinterlinked.com/events/ – it works better, but not fully. It will not allow me to “finalize registration”. I am going to try to deactivate and then re-activate and see what happens.
WP Engine does not support WP HTTPS plugin. They have their own internal way to secure pages.
|
|
Delray Wannemcher
|
March 3, 2014 at 3:04 pm
I deactivated and then reactivated and the problem still persists.
I get two different error messages depending on which page I try to register:
With Shortcode:
An error has occurred:
We’re sorry but your request failed to pass a security check.
Please click the back button on your browser and try again.
TCKSLC-DTCKSLC-PROTICSEL-227
No shortcode, on /events page:
An error has occurred:
Your form data could not be applied to any valid registrations.
SNGPGCHC-DSNGPGCHC-PROATTINF-1271
Some of the events not using a shortcode give the error, but others do not. I was just able to successfully register from /events for an event but only via Invoice. When I tried via Credit Card, the “Finalize Registration” button seemed disabled.
|
|
Delray Wannemcher
|
March 3, 2014 at 3:16 pm
Does the licensing key have any effect on this problem? It was added on staging so we could update to the newest version before migrating. Where should the key now be stored: staging or production? And how do you recommend we handle this?
|
|
Brent Christensen
|
March 3, 2014 at 5:00 pm
Hi Delray,
Pretty certain this is a caching issue.
When I go to http://www.fsxinterlinked.com/events/ and add some tickets then click “Register Now”, I get taken to the Registration Checkout page at https://www.fsxinterlinked.com/registration-checkout/?ee=_register
but it displays a “Nothing in your Event Queue” message, meaning EE could not connect your current session with a valid Cart object on our end of things.
But here’s the thing…
If I click my browser’s back button… all of my event list form options are still selected (they SHOULD be cleared) and if I simply click the “Register Now” button again without doing anything else, then I get taken to the Registration Checkout page again, but THIS TIME… the registration form shows up correctly.
So in other words, content that should appear doesn’t until you revisit the page a second time, and content that should be gone, is still there. This just screams caching issue to me.
Please note that your registration checkout page is protected by SSL so you will have to ensure that caching is turned off for the HTTPS version of that page (https://www.fsxinterlinked.com/registration-checkout).
As well, you should also turn off caching for these URLs:
http://www.fsxinterlinked.com/events/ (and subpages)
https://www.fsxinterlinked.com/transactions/
http://www.fsxinterlinked.com/thank-you/
|
|
Brent Christensen
|
March 3, 2014 at 5:06 pm
OH… I forgot to mention…
I also get the following errors popping up in my browser’s console when taken to the registration checkout page that successfully displays the reg form:
Blocked loading mixed active content “http://www.fsxinterlinked.com/wp-content/themes-ai1ec/vortex/style.css?ver=1.10.5-8”
Blocked loading mixed active content “http://www.fsxinterlinked.com/wp-content/themes-ai1ec/vortex/css/event.css?ver=1.10.5-8”
Blocked loading mixed active content “http://www.fsxinterlinked.com/wp-content/themes-ai1ec/vortex/style.css?ver=1.10.5-8”
Blocked loading mixed active content “http://www.fsxinterlinked.com/wp-content/themes-ai1ec/vortex/css/event.css?ver=1.10.5-8”
those errors don’t affect EE at all, but they are indicative of loading issues,
so it looks like some other stuff is getting messed with as well.
|
|
Delray Wannemcher
|
March 3, 2014 at 5:37 pm
Thanks Bret. I am going to confirm with WP Engine that the caching is disabled for those pages. I previously requested it, and they said it was disabled, but apparently not.
|
|
Brent Christensen
|
March 3, 2014 at 5:41 pm
Here’s a couple other things that might possibly be interfering with things (although I still think there’s caching issues)
#1) It looks like your Eventor theme is de-registering the version of jQuery that is included with WP 3.8.1 (jQuery version 1.10.2) and replacing it with a minified version of jQuery 1.7.2 (which was released in March of 2012).
Swapping out the current core version of jQuery for a version that is 2 years old is really frowned upon because it is a sure fire way to break all kinds of things in WP. You should either contact your theme developer about this and/or hire a developer to remove the code that de-registers the core version of jQuery. This latter option could of course break your theme if it is relying on 2 year old code.
#2 You have over 60 JavaScript files running on the Registration Checkout page including nearly every single component for the jQuery UI library, although I can’t fathom what that would be needed for on that page. You should also try to figure out a way to restrict the number of scripts loading on each page, as this can help greatly in preventing conflicts.
|
|
Delray Wannemcher
|
March 4, 2014 at 7:20 am
Hi Bret,
WP Engine has assured me that caching has been disabled for the requested pages. But they informed me that it is only disabled on those pages. So, if there is an argument created or a cookie that should also be prevented from caching, they will need to know which ones specifically so those can also be excluded from caching.
Please let me know which cookies and/or arguments should be excluded.
Thanks
|
|
Josh
|
March 4, 2014 at 9:27 am
Hi Delray,
Can you ask for clarification as to what “arguments” means?
Event Espresso 4 does not store anything in cookies for security reasons.
|
