|
Allen
|
February 23, 2022 at 3:38 pm
Hi there, I get fatal and crictical errors caused by your plugin. I’ve made note of it before. Here is what tech support from my hosting company provided.
Maybe this will help you diagnose or fix this problem.
It looks like that critical error was caused by the plugin event-espresso-core-reg, here is the error in its entirety including the stack trace:
PHP Fatal error: 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 244 and defined in /www/wp-content/plugins/event-espresso-core-reg/core/domain/entities/custom_post_types/CustomPostTypeDefinitions.php:258
Stack trace:
#0 /www/wp-content/plugins/event-espresso-core-reg/core/domain/entities/custom_post_types/CustomPostTypeDefinitions.php(244): 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(739): 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 in /www/wp-content/plugins/event-espresso-core-reg/core/domain/entities/custom_post_types/CustomPostTypeDefinitions.php on line 258
From here, it would be best to reach out to the plugin developers about this fatal error, as I’m sure this also played a part in the err_connection_closed errors seen previously. The developer will be able to provide some plugin-specific troubleshooting to help get this cleared up.
If you have any other questions or concerns, don’t hesitate to reach out!
|
|
Tony
|
February 24, 2022 at 2:51 pm
Hi Allen,
I checked into this and something is hooking into the EE save_post call and doing something strange above, it’s then causing the above fatal error.
We are going to add some additional checks into the function to prevent the fatal from happening in the future, this will likely be included in the next version of Event Espresso (due out early next week).
However…
From here, it would be best to reach out to the plugin developers about this fatal error, as I’m sure this also played a part in the err_connection_closed errors seen previously.
I’m not so sure the above error has anything to do with the err_connection_closed errors so it the host is assuming fixing the above error will prevent those I’m not really sure how.
|
|
Brent Christensen
|
March 8, 2022 at 1:17 pm
fix has been merged to master
|
