Support

May 20, 2021 at 2:59 pm

To confirm, what actually happens with the registrations when this happens? Do they site pending payment or are they simply not in the system at all?

But why would that happen if there’s caching?

Basically, when EE says ‘Create a new transaction’ that’s exactly what would normally happen, a new transaction, registration etc is create in the database etc.

With caching, it sits in the middle (it depends on the type of caching which is why I keep asking for more details on the type of caching enabled) and when EE says ‘create a new transaction’ the caching function says “Hey! I already have one of those from someone else, use this”… that’s not a good thing to happen with ecommrce.

UPDATE:
The website has 2 caching system – Managed WordPress and the WP Rocket.

Ah, so you’re using a GoDaddy Managed WordPress site? We don’t recommend GoDaddy and especially their Managed WordPress package with Event Espresso.

We had far to many reports of users getting conflicting answers from GoDaddy, they force server side caching on all pages and one service rep says you can disable it doing X, another says do Y and then others simply say you can’t disable it. Add the fact that for those that then said it could be disabled and we followed the steps they provided…. only for it then randomly be enabled again on users site without warning and you start to see why we recommend why you don’t use GoDaddy Managed WordPress.

I changed the settings to “Site caching (using your site headers)”. There is a Disabled but I didnt choose that. It might slow the site.

IF GoDaddy respect the headers, that might work, but it’s very much dependent of if they do, see above.

Slowing the site is better than what is happening now, I recommend disabling it.

May 20, 2021 at 4:24 pm

>> No transaction or registration at all. The student is not in the system- no trace but she was able to buy a ticket thru Paypal.

Yeah, so the only time I see that happen, is caching.

As above, EE tries to create a new object and the caching layer sits and returns a previous one. EE then uses it as it would (it’s none the wiser) and what is happening is the same ID’s are being used in the database, meaning that basically each registration is overwriting the last one.

You see them in PayPal because they are outside of your EE install there.

>> My admins are complaining that it never happened all these quirky until I upgraded it to Managed WordPress.

From what we’ve seen, that’s not uncommon.

In short, the difference there will be caching. GoDaddy Managed WordPress accounts force caching on all pages by default.

I very rarely comment on hosting with a particular company (if you search the forums you’ll see I actively avoid doing so), they all have pros and cons and often it’s down to the individual. However, I simply do not recommend GoDaddy hosting, especially their Managed WordPress packages with Event Espresso.

>> It just so happened we have a deluxe security we only enabled the firewall last night.

A firewall shouldn’t cause issues like this unless that’s also doing some weird caching.

May 20, 2021 at 4:28 pm

That’s likely just for page caching but all of the critical pages listed under:

Event Espresso -> General Settings -> Critical Pages.

See: https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/

However, note that GoDaddy will very likley have object and database caching enabled, I’m not sure if they exclude those on specific pages with the above.

May 24, 2021 at 7:09 am

Hi there,

Did Tony’s suggestion work for you?