|
vivogroup
|
June 29, 2017 at 5:23 pm
Hi Support!
We’re getting the “It appears your browser is not currently set to accept Cookies” error on the /registration-checkout pages after selecting a ticket type in the ticket form and proceeding to checkout.
The site is hosted on pantheon.io – are you aware of any compatibility issues that would prevent EE from working on Pantheon?
We’re using the following EE plugins/versions:
Event Espresso - Version 4.9.34.p
Event Espresso - People Addon (EE 4.5+) - Version 1.0.5.p
Event Espresso - Version 1.0.10.p
Event Espresso - Stripe Gateway (EE 4.6.0+) - Version 1.0.14.p
Event Espresso - WP Users (EE4.6+) - Version 2.0.14.p
We’ve ensured the EE pages are excluded from the pantheon cache and also tried add the add_filter( 'FHEE__EE_Front_Controller____construct__set_test_cookie', '__return_false' ); filter without any luck.
Any other ideas or is this a known issue on this platform?
Thanks for your help.
|
|
Tony
|
June 30, 2017 at 7:24 am
Hi there,
Are you running any caching plugins?
Looking at the headers for your site it looks like the server has Varnish caching enabled, have the EE checkout pages been excluded from the server side caching?
https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/
|
|
vivogroup
|
July 2, 2017 at 4:45 pm
Thanks Tony.
We don’t have any extra caching plugins. Pantheon does have varnish as you can see but we’ve excluded the EE pages from this which Pantheon have confirmed is working correctly.
The test link is:
https://dev.profitablehospitality.com.au/events/test-event/
curl -IL https://dev.profitablehospitality.com.au/registration-checkout/?uts=1498729658#checkout
HTTP/1.1 200 OK
Date: Fri, 30 Jun 2017 07:19:05 GMT
Connection: keep-alive
Content-Type: text/html; charset=UTF-8
Link: <https://dev.profitablehospitality.com.au/wp-json/>; rel="https://api.w.org/"
Link: <https://dev.profitablehospitality.com.au/?p=1063>; rel=shortlink
Server: nginx
Set-Cookie: SESSac20fd56ed1dc190081e3d9ece4b69c3=34dacc540c41be705421ed2317ca8c9b; expires=Fri, 30-Jun-2017 07:19:02 GMT; Max-Age=-1
Set-Cookie: SSESSac20fd56ed1dc190081e3d9ece4b69c3=457bf4a1ea1101479f4f2f1036be9601; path=/; domain=.dev.profitablehospitality.com.au; secure; HttpOnly
Surrogate-Key-Raw:
X-Pantheon-Styx-Hostname: styx96f33d0e
X-Styx-Req-Id: styx-18bcebcdebeda92f05ee22400f8229ce
Via: 1.1 varnish
Fastly-Debug-Digest: 9fb506c09059746dea952382972f33efe79707eb4c66bf5ecdd6c8c898d83b8c
Cache-Control: no-cache, must-revalidate, post-check=0, pre-check=0
Accept-Ranges: bytes
Via: 1.1 varnish
Age: 0
X-Served-By: cache-ord1727-ORD, cache-lax8629-LAX
X-Cache: MISS, MISS
X-Cache-Hits: 0, 0
X-Timer: S1498807141.153787,VS0,VE4748
Vary: Accept-Encoding, Cookie, Cookie
Any other ideas?
|
|
vivogroup
|
July 2, 2017 at 4:59 pm
FYI – I just noticed there was an updated version of EE and a couple of the addons so updating those seemed to resolve it so must have been an issue in the versions we were running.
|
|
vivogroup
|
July 2, 2017 at 5:36 pm
So looks like I jumped the gun – it worked the first time after updating the plugins but is now still showing the Cookies error when trying to checkout.
Thanks again for taking a look!
|
|
vivogroup
|
July 2, 2017 at 5:58 pm
Premimum support ticket raised
|
|
Josh
|
July 3, 2017 at 7:53 am
Hi there,
Tony followed up with an email, did you get the email he sent?
I’ll add that the http headers indicate that the registration-checkout page is still being served via proxy with Varnish. Can that be configured to bypass Varnish?
|
|
vivogroup
|
July 5, 2017 at 5:37 am
Hi Josh,
In then end the issue seemed to be caused by a need to rebuild the checkout slugs.
Within Pantheon it’s not possible to amend the Varnish config, only clear it and request that no browser cache is utilised – https://pantheon.io/docs/cache-control/
Thanks,
Ross
|
|
Tony
|
July 5, 2017 at 6:43 am
Can you explain a little further on what you mean by ‘rebuild the checkout slugs’ please?
You mean re-creating the checkout page and saving the new page as the Registration Checkout critical page?
|
|
vivogroup
|
July 5, 2017 at 10:07 pm
Hi Tony/Josh,
Thanks for your help.
The issue with the cookies error was the way we were forcing EE to use /events as the slug base rather than /blog/events. This has been fixed.
The next issue we’re now facing is the payment options step sometimes being empty/blank which is seemingly random. Once attendee form is filled, proceeding to the next step presents a blank space underneath the Steps and a Proceed to Finalize Registration button which obviously doesn’t work since a payment option hasn’t been selected.
Any ideas? I’ve got Pantheon looking into confirming the caching is excluded properly as per their documentation:
https://pantheon.io/docs/cache-control/
https://pantheon.io/docs/caching-advanced-topics/
Cheers,
Sam
|
|
Josh
|
July 6, 2017 at 7:25 am
If you make any changes to the Registration Checkout page (like add some text to the page’s editor box) then refresh the page in a logged out window does the change appear?
|
|
vivogroup
|
July 6, 2017 at 4:32 pm
Yeah making a change to the page and refreshing in incognito the change appears…
|
|
Tony
|
July 7, 2017 at 4:46 am
Hmm, any errors in the error logs?
You may need to enable WP_DEBUG on the site to log the errors.
You can use a snippet like this:
https://gist.github.com/Pebblo/8787f5530ea777c84aaf62f075e55b32
Within your wp-config.php file to log any errors to /wp-content/debug.log
|
|
vivogroup
|
July 10, 2017 at 3:32 am
Hi all,
Another piece of info from Pantheon – we asked why we saw “MISS/HIT” in response headers in relation to Varnish Cache after excluding Event Espresso resources. We were provided with the following:
The MISS/HIT indicates the js assets are being served from the second level cache.
Layer 1 is the closest possible to your location. Layer 2 is what you see in X-Served-By, first position this way, if the first layer misses, there’s still a chance the content gets served from the second layer.
Disabling caching for any assets that don’t hit the php worker would need changes in nginx.conf, which isn’t possible.
Can you feed that back to the plugin authors to comment please.
Kind regards
Mike Richardson
Lead Technical Support Engineer
https://pantheon.io
|
|
Josh
|
July 10, 2017 at 8:06 am
It sounds like they don’t have a solution that will work with Event Espresso 4’s dynamic checkout.
|
|
vivogroup
|
July 11, 2017 at 4:51 am
Hi Josh,
We’re in a difficult situation here I’m afraid because the choice of Pantheon as hosting provider has been made for various brands and countries within our company (Silver Chef Limited). It provides a lot of benefits in terms of release and change management. Therefore, it’s not an option to host elsewhere.
Within Pantheon’s dev environment there is no issue; the process works every time. We had asked why dev always worked and received the following reply:
“Assets (cs/js/etc.) aren’t cached in dev, so that seems to be relevant.
Can you ask the author plugin why the cached assets (which seems to be a js file) breaks the plugin.
It’s an anti-pattern not to cache static assets and goes against best practices in general.
If they can narrow down where this is occurring and work around it, it would enable many people to use the plugin on the platform.
Unfortunately, we don’t have the option of varying the Varnish vcl on a site-by-site basis.
Kind regards
Mike Richardson
Lead Technical Support Engineer
https://pantheon.io”
Is there absolutely no workaround here? We’re close to having to look elsewhere to meet our events plugin needs but have put in a lot of effort already with Event Espresso and would obviously really like to avoid such this scenario.
Thanks,
Ross
|
|
Josh
|
July 11, 2017 at 8:01 am
Hi Ross,
Normally caching the JS assets does not break Event Espresso’s functionality. I’m not convinced that caching JS is the cause of the problem, the problem doesn’t happen everytime correct? When the payment step returns a blank page are you seeing any JavaScript errors in the console? Does Pantheon support have a support tech that can look at the server logs for when the blank pages occurred?
One thing that might help, and this is only a guess based on the very limited knowledge of the situation, is you can try encoding the session data. You go to Event Espresso > General Settings > Admin Options and set Encode Session Data to Yes then save the page.
|
|
vivogroup
|
July 11, 2017 at 6:21 pm
Hi Josh,
Unfortunately enabling that option hasn’t resolved the issue.
It’s difficult for me to explain the exact scenario in which the payment steps do not appear, but if usually if I clear browser cache or do a hard refresh (ctrl+F5) the payment details appear.
Cheers,
Ross
|
|
Josh
|
July 12, 2017 at 7:54 am
Hi Ross,
Your reply didn’t answer any of the questions I asked. Maybe you and Pantheon can work out getting an account set up where Event Espresso staff can investigate further? We’d need full access to a server where we’d have no restrictions to make changes, and this would need to be a live environment (because there are no issues on Pantheon’s dev environment).
It would also be helpful if Pantheon can provide some specific documentation about how they have caching set up on the live environment, and how the caching can be excluded/disabled/bypassed.
|
