Support

January 14, 2019 at 8:21 am

Hi Faith,

Just to note, regardless of any issues with the license key, you can always update Event Espresso manually, we have instructions on doing so here:

https://eventespresso.com/wiki/how-to-upgrade-event-espresso/#ee4-manual-update

It’s basically de-activate and delete the current version (all of you event and related details are saved to the database, not the plugin so you won’t lose any data, but its good practice to do a database backup first just to be safe)

Download the latest version from your account page and upload through Dashboard -> Plugins -> Add new -> Upload plugin, then activate.

I wrote to you just now and asked that the license that was on the old staging site (wyrecommunity.wpengine.com) be applied to this site so that I could do this upgrade urgently

We don’t actually assign the domain to your key, its done automatically when your site pings out servers and you have a key set in Event Espresso. If the key is already set and a different site pings with that key, its flags up (Little more to it than that, but that’s the general idea).

I’ve reset your license key, if you go to Event Espresso -> General Settings on the LIVE site and save, the key should be assigned to that domain and you can update…

You’ll need to remove the key from the staging site now to prevent the above from happening again. (Just set the key field to nothing and save)

When I tried to update EE it said my Elegant Themes API is wrong. These are the people who make the Divi theme that I use and the API is correct. Not sure why this should affect my EE update anyway??

In short, that’s because elegant themes are hijacking the request.

One way or another I need to be able to sort the issue of EE not working on the live site URGENTLY! I’m guessing getting the updates done will be the first thing to try?

What has changed on the live site between when registrations worked and now?

On the live site:

If you go to Event Espresso -> General Settings -> Crticial pages do they all show as Page Status and Shortcode ‘OK’?

Unless someone has renamed the ‘registration-checkout’ page, it looks like that page has been removed or no longer published publicly?

January 14, 2019 at 10:58 am

Hi Faith,

You can contact WPEngine support and ask them to add cache exclusions for the Critical pages. The registration Checkout page on your site is showing it’s being cached by the wpengine servers.

There’s more information here:
https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/

January 14, 2019 at 11:52 am

They need to do more than clear the cache. They need to add cache exclusions, and they’ll need to confirm from their end whether the cache exclusions have been added.

January 15, 2019 at 11:40 am

But if the appropriate pages are excluded anyway, why should that matter?

It doesn’t appear that they are excluded. Their http response headers would be different if they were excluded.

I have another site at the moment with the same settings/plugins/theme version/wordpress version and there is no problem on that – https://dreamingawake.co.uk

Here’s a screenshot of that site’s response headers from its registration-checkout page:

https://slack-files.com/T02SY781D-FFE5B5EP6-eee452e289

You’ll note there are different values for the x-cache headers there.

when I am logged into the site I can book a course no problem. I just tried on my partner’s computer though and got the same issue that the client is getting.

That’s because of the caching. When you’re logged into the site, you’re not getting pages served from the cache. It’s only when you’re logged out that you’ll get served from a cache when it’s a WPEngine site.

I’m afraid this isn’t something we can fix from our end. WPEngine will need to update the site so the registration-checkout pages are excluded from being cache.

January 15, 2019 at 11:47 am

Those are unrelated because that’s happening on a different page. The page that you’re having problems with is the registration-checkout page.

January 15, 2019 at 12:03 pm

Do you think the course page itself should be added to the cache exclusions- the one with this sort code on it[ESPRESSO_EVENTS sort=ASC] to display the list of events?

That’s optional. Where caching would make a difference there is if an event sold out or was expired, the information could be out of date if caching is turned on. The page will load a bit quicker if caching is left on.

January 15, 2019 at 12:56 pm

I’m guessing that even if this is possible then it will have downsides – eg all the EE pages will be slower to load?

They’ll be the same speed to load as when you’re logged in to the site. Generally, caching can be used to speed things up a bit if the page content is static. It’s not really a viable option if the page needs to serve dynamic content, like a checkout page.