Support

September 13, 2024 at 1:37 pm

Hi there,

This:

There has been a critical error on this website. Please check your site admin email inbox for instructions

Is the ‘pretty’ version of a fatal error, WordPress shows that on front end when the error is thrown but your server should log the ‘real’/’full’ error in the error logs.

We need that error to be able to troubleshoot this as the above could be related to anything currently.

My host is suggesting I don’t activate EE again, but, of course, that is not something I want to do.

Thats a “we can’t be bothered helping” kind of answer and personally, would have me questioning if it’s the right host to use.

Without the full error I can’t tell you whats happening, but your hosts control panel will often have a section to view PHP errors on the server. Check for those, search for ‘fatal error’, post that here.

Do you have FTP/File Maneger access?

September 16, 2024 at 5:29 am

Hmm, ok, strange.

Which specific version number of Event Espresso do you currently have installed?

I’d like to take a look at this but I’ll need both WP Admin and FTP credentials to troubleshoot, if you are ok with sending those over you can do so using this form:

https://eventespresso.com/send-login-details/

September 18, 2024 at 4:44 am

Hi there,

I’ve updated Event Espresso to 5.0.26.p and that has fixed the issue on your site, however, I can’t see why that fixed it so I’ve asked one of our developers if they have any feedback so I can double check.

I don’t want to say it’s all fixed and then you get the same issue on the next update so I’m trying to figure out how it happened (I can’t reproduce this locally).

September 18, 2024 at 7:05 am

You’re most welcome 🙂

I’ll let you know with whatever feedback the developers come back with here.

October 15, 2024 at 2:08 pm

Yes, thank you.

We can see why the code failed but not what caused the condition for it to happen, so we’ve applied a fix within core to prevent it from happening again and will so that goes and if more investigating is required from there.

October 15, 2024 at 3:18 pm

You’re most welcome.

If you run into any further issues, please do let me know.

Hopefully not and have a great week!

November 25, 2024 at 3:16 am

Hi there,

Those notices/warnings generally wouldn’t prevent the page from loading.

The 7 notices:

Notice: Function _load_textdomain_just_in_time was called incorrectly....

Are related to translations loading early on the request, the translations should still work but they now also throw a notice to say they are loading too early (this was a change in WP6.7 and they’ve also pushed a fix where translations wouldn’t load at all in 6.7.1).

The last 3 warnings all related to headers being sent:

Warning: Cannot modify header information – headers already sent...

Those are happening because the above notices are being sent tho the browser (you can’t start a session if something has been sent to the browser and those notices are).

However, none of that should prevent the page from loading.

Which site is this happening on?