|
Allen
|
February 1, 2021 at 3:06 pm
I get a Fatal Error gray screen message quite often – seems to happen after making changes to an event, such as date or number of tickets available.
Wordpress sends me the following email, indicating EE is causing the error.
Each time it happens, I simply hit “back”, make all the changes again, then hit “update” – and it works fine.
Not sure what the problem is, maybe you can figure it out. Error message shown below – with what appears to be an Error Log at the end.
I’ve had this problem before, and have posted before – and last time you told me to locate an error log — is this what you need?
*****
Howdy!
Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, Event Espresso.
First, visit your website (https://superbilliardsexpo.com/) and check for any visible issues. Next, visit the page where the error was caught (https://superbilliardsexpo.com/wp-admin/post.php) and check for any visible issues.
Please contact your host for assistance with investigating this issue further.
If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.
To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.
When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.5.3
Current theme: Hello Child (version 1.0)
Current plugin: Event Espresso (version 4.10.10.p)
PHP version 7.4.13
Error Details
=============
An error of type E_ERROR was caused in line 257 of the file /www/wp-content/plugins/event-espresso-core-reg/core/domain/entities/custom_post_types/CustomPostTypeDefinitions.php. Error message: Uncaught TypeError: Argument 2 passed to EventEspresso\core\domain\entities\custom_post_types\CustomPostTypeDefinitions::getCustomPostTypeModelName() must be of the type array, null given, called in /www/wp-content/plugins/event-espresso-core-reg/core/domain/entities/custom_post_types/CustomPostTypeDefinitions.php on line 243 and defined in /www/wp-content/plugins/event-espresso-core-reg/core/domain/entities/custom_post_types/CustomPostTypeDefinitions.php:257
Stack trace:
#0 /www/wp-content/plugins/event-espresso-core-reg/core/domain/entities/custom_post_types/CustomPostTypeDefinitions.php(243): EventEspresso\core\domain\entities\custom_post_types\CustomPostTypeDefinitions->getCustomPostTypeModelName(false, NULL)
#1 /www/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_CPT.core.php(741): EventEspresso\core\domain\entities\custom_post_types\CustomPostTypeDefinitions->getCustomPostTypeModelNames(false)
#2 /www/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_CPT.core.php(85
|
|
Tony
|
February 8, 2021 at 8:35 am
Hi there,
Yes, the error you posted is what we need, however, I’ve been investigating this and can’t reproduce.
Right now I’m guessing that something else is hooking into the update and altering a value that we use to something unexpected but without being able to reproduce its difficult to say.
Would it be possible to take a look at the site and if anything stands out on the request? If so I’ll need temp login details for that site which you can send using this form:
https://eventespresso.com/send-login-details/
Note that if you can include FTP credential I can add some debug code into Event Espresso to see if narrows the problem further.
|
