Support

February 9, 2021 at 6:07 am

Hello.

Earlier today we moved our site to Kinsta Managed WordPress hosting service (we already host plenty of sites there with success).

After the migration, we QAed the site and found out that it was not working properly. We had to switch the IP back to the old host.

Before describing the issues, I am listing here the cache exclusion rules that we had already applied on the new server.

^/registration-checkout
^/transactions
^/thank-you
^/registration-cancelled
^/account
^/checkout-login
^/dashboard
^/login
^/logout
^/register
^/lostpassword
^/resetpass
^/account/profile
^/events

Also, our payment provider is Authorize.net.

Our EE is Version 4.10.10.p
*

The primary issue is that the checkout did not work. We did 2 separate checkout attempts and we received the following:

https://prnt.sc/yud25m
https://prnt.sc/yud69q

Also, we had another issue, which led us to disable cache for all Events pages.

If I added 0 tickets to the event cart, the page had to reload and show the following message:

https://prnt.sc/yudh0g

This sounds correct, Kinsta’s nginx server was caching it. As a result, all guest visitors would see this message if another person had previously hit this button with 0 tickets.

So, we had to exclude all /events/xxxxx URLs from the cache, which fixed the issue. This is not ideal (we do want to cache as much as possible for better performance), so I would like to ask if there is a cookie that is set by Event Espresso at this action so that we can exclude this specific cookie from the cache.

*

I have reached Kinsta’s support for all this. They are happy to help but they are saying they do not have issues with other clients running Event Espresso.

So, at this point, I am not sure where to start in order to debug this.

Please let me know if you can help.

Thanks in advance