|
Staggers
|
May 2, 2024 at 1:56 pm
Hi there. I could do with a steer. I’ve had a few problems with the site since PHP was upgraded a while back. Anyhow, I’m trying to activate EE and I’m getting complete site maLfunction. I can submit error logs but the headline is a series of “Uncaught TypeError”‘s. I recently changes the db password which necessitated a manual update of the wp_config.php file. I am wondering whether there are knock-on effects to the EE config files?
Many thanks in advance
John
|
|
Tony
|
May 2, 2024 at 4:35 pm
Hi John,
Do you have the full error being thrown?
If so can you either add them here or send them over to support@eventespresso.com so I check into them, please?
|
|
Staggers
|
May 2, 2024 at 8:51 pm
This reply has been marked as private.
|
|
Tony
|
May 3, 2024 at 2:25 am
PHP Fatal error: Uncaught TypeError: EventEspresso\core\services\orm\ModelFieldFactory::createEmailField(): Return value must be of type EE_Email_Field, EE_Email_Field returned
Hmmm… so that says…
“X must return a EE_Email_Field, but itstead it returned a EE_Email_Field”
So, a fatal to say it did what it should do? Weird :S
—
So, let’s start with the basics.
First, try to reinstall Event Espresso again, download the .zip from your account page and upload it through Dashboard -> Plugins -> Add new -> Upload plugin.
WordPress should tell you there is a version already installed and ask if you want to overwrite it. Do so.
(Note, unfortunately I don’t think that’s going to fix this but it at least makes sure your running a clean copy installed through the admin and not FTP etc)
Next, any object cached enabled on the site?
Or any caching for that matter?
Which PHP version?
I recently changes the db password which necessitated a manual update of the wp_config.php file. I am wondering whether there are knock-on effects to the EE config files?
No, changing the DB password is fine.
May I ask why it was needed? Changing the password wont cause issues like this, updating the wp-config.php wouldn’t usually… but… whatever reason caused the need for those changes may well be related.
|
|
Staggers
|
May 3, 2024 at 3:17 am
Hi Tony
OK, reinstalled. The front end displays this so I have deactivated it for now:
Fatal error: Uncaught TypeError: EventEspresso\core\services\editor\BlockRegistrationManager::__construct(): Argument #1 ($block_asset_manager_collection) must be of type EventEspresso\core\services\assets\BlockAssetManagerCollection, null given in /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/services/editor/BlockRegistrationManager.php:61 Stack trace: #0 [internal function]: EventEspresso\core\services\editor\BlockRegistrationManager->__construct() #1 /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/EE_Registry.core.php(1308): ReflectionClass->newInstanceArgs() #2 /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/EE_Registry.core.php(800): EE_Registry->_create_object() #3 /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/services/loaders/CoreLoader.php(109): EE_Registry->create() #4 /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/services/loaders/CachingLoader.php(157): EventEspresso\core\services\loaders\CoreLoader->load() #5 /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/services/loaders/Loader.php(81): EventEspresso\core\services\loaders\CachingLoader->load() #6 /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/services/loaders/Loader.php(104): EventEspresso\core\services\loaders\Loader->load() #7 /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/domain/entities/routing/handlers/shared/AssetRequests.php(147): EventEspresso\core\services\loaders\Loader->getShared() #8 /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/services/routing/Route.php(229): EventEspresso\core\domain\entities\routing\handlers\shared\AssetRequests->requestHandler() #9 /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/services/routing/RouteHandler.php(141): EventEspresso\core\services\routing\Route->handleRequest() #10 /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/services/routing/RouteHandler.php(96): EventEspresso\core\services\routing\RouteHandler->handle() #11 /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/services/routing/Router.php(218): EventEspresso\core\services\routing\RouteHandler->addRoute() #12 /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/EE_System.core.php(1133): EventEspresso\core\services\routing\Router->coreLoadedAndReady() #13 /homepages/1/d4296723504/htdocs/wordpress/wp-includes/class-wp-hook.php(324): EE_System->core_loaded_and_ready() #14 /homepages/1/d4296723504/htdocs/wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #15 /homepages/1/d4296723504/htdocs/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action() #16 /homepages/1/d4296723504/htdocs/wordpress/wp-settings.php(695): do_action() #17 /homepages/1/d4296723504/htdocs/wordpress/wp-config.php(192): require_once(‘/homepages/1/d4…’) #18 /homepages/1/d4296723504/htdocs/wordpress/wp-load.php(50): require_once(‘/homepages/1/d4…’) #19 /homepages/1/d4296723504/htdocs/wordpress/wp-blog-header.php(13): require_once(‘/homepages/1/d4…’) #20 /homepages/1/d4296723504/htdocs/wordpress/index.php(17): require(‘/homepages/1/d4…’) #21 {main} thrown in /homepages/1/d4296723504/htdocs/wordpress/wp-content/plugins/event-espresso-core-reg/core/services/editor/BlockRegistrationManager.php on line 61
Will send further info on your questions shortly.
John
|
|
Staggers
|
May 3, 2024 at 3:26 am
Your questions:
1. PHP is 8.2
2. I’m afraid I do not know the answer to your cache quesiton. I have not set up caching but I am a novice user.
3. I did not need to change the db password for what I wanted to acheive so I think this is incidentla. I was hitting a file number limit and deleted a number of files (which I thought may be a cause of the EE issue). This caused a fatal crash and I carried out a restore.
4. I am using Elementor and there seems to have been some conmflict between the two (deactivated Elementor and EE worked and vice versa).
John
|
|
Tony
|
May 3, 2024 at 4:33 am
So the above is only caused when Elementor is active along with EE or is that a different issue?
Can I take a look at the site? If so send temp login details over using this form:
https://eventespresso.com/send-login-details/
I’d also like to rule out a server config issue and the quickest way to do that is for me to clone the site locally and test it here, are you ok with me doing that?
|
|
Staggers
|
May 3, 2024 at 5:03 am
There does seem to be a conflict between the two. I have now deactivated Elementor and activated EE. The site does not crash but EE does not operate correctly.
Very happy (and grateful) for your help and have sent temp login credetials. Happy for you to clone the site locally.
John
|
|
Rio
|
May 7, 2024 at 1:55 am
Im looking on your site, and it seems you’re encountering Internal Server at the moment. Before we touch anything, are you working on your site? Do you have staging site we can debug to avoid some conflicts. We don’t want to change what you’re currently doing on your site.
thanks.
|
|
Tony
|
May 7, 2024 at 6:41 am
Hi John,
My apologies for the delay reply from myself.
I’ve emailed with some details specific details relating to your site rather than posting them here but just to provide some context for any additional readers, the short of it is I think this is a server-side/config related issue.
The errors you are getting just don’t make sense:
PHP Fatal error: Uncaught TypeError: EventEspresso\core\services\orm\ModelFieldFactory::createEmailField(): Return value must be of type EE_Email_Field, EE_Email_Field returned
Must be of type EE_Email_Field but EE_Email_Field was returned?
Fatal error: Uncaught TypeError: EventEspresso\core\services\editor\BlockRegistrationManager::__construct(): Argument #1 ($block_asset_manager_collection) must be of type EventEspresso\core\services\assets\BlockAssetManagerCollection, null
This one is possible, but, looking over your error logs your getting memory exhausted errors so it could also be related to that here, we can investigate this further but need the current issues resolved first.
Right now the site is throwing an error related to Elementor not extending a class, this:
PHP Fatal error: Uncaught Exception: 'Elementor\Core\Frontend\RenderModes\Render_Mode_Normal' must extend 'Render_Mode_Base'
But that class does indeed extend the base class referenced so another that doesn’t really make any sense.
—-
My best guess is currently something going on with OPCache, Object Caching or some other form of caching on the server. I can’t think of anything else that would cause these errors from valid code, note I’m not just stating EE’s code is valid but also Elementors, yet both cause fatal on that server.
|
