|
spirometry
|
May 17, 2022 at 4:51 am
I have just migrated my WordPress website across to a new host, and they had to deactivate the event-espresso-core-reg plugin as it was causing “critical error on this website” So they tried re-installing the plugin, and re-transferring it but to no avail. They recommend I contact you for further investigation on the matter . Could you please advise how to overcome this? it seems like it is not uncommon, according to the threads. Thanks in advance
|
|
Tony
|
May 17, 2022 at 9:22 am
Hi there,
The “critical error on this website” error is a ‘front-facing’ catch-all error, it means somewhere on the site the code running threw an error and rather than showing the debug info the above was shown.
However, to know what the problem is we need the actual error being thrown rather than that front-facing error.
Do you have access to the error logs?
Or can your new host provide the error being thrown from within the logs?
|
|
spirometry
|
May 17, 2022 at 3:40 pm
Here you go, this is what they received:
[17-May-2022 10:29:54 UTC] PHP Fatal error: Uncaught EventEspresso\core\exceptions\InvalidAliasException: "EventEspresso\core\services\cache\CacheStorageInterface" can not be used as an alias because the "EventEspresso\core\services\cache\TransientCacheStorage" class does not extend or implement it. in /wp-content/plugins/event-espresso-core-reg/core/services/loaders/ClassInterfaceCache.php:91
Stack trace:
#0 /wp-content/plugins/event-espresso-core-reg/core/EE_Dependency_Map.core.php(1118): EventEspresso\core\services\loaders\ClassInterfaceCache->addAlias('EventEspresso\\c...', 'EventEspresso\\c...')
#1 /wp-content/plugins/event-espresso-core-reg/core/EE_Dependency_Map.core.php(113): EE_Dependency_Map->_register_core_aliases()
#2 /wp-content/plugins/event-espresso-core-reg/core/services/bootstrap/BootstrapCo in /wp-content/plugins/event-espresso-core-reg/core/services/loaders/ClassInterfaceCache.php on line 91
[17-May-2022 10:31:28 UTC] PHP Fatal error: Uncaught EventEspresso\core\exceptions\InvalidAliasException: "EventEspresso\core\services\cache\CacheStorageInterface" can not be used as an alias because the "EventEspresso\core\services\cache\TransientCacheStorage" class does not extend or implement it. in /wp-content/plugins/event-espresso-core-reg/core/services/loaders/ClassInterfaceCache.php:91
Stack trace:
#0 /wp-content/plugins/event-espresso-core-reg/core/EE_Dependency_Map.core.php(1118): EventEspresso\core\services\loaders\ClassInterfaceCache->addAlias('EventEspresso\\c...', 'EventEspresso\\c...')
#1 /wp-content/plugins/event-espresso-core-reg/core/EE_Dependency_Map.core.php(113): EE_Dependency_Map->_register_core_aliases()
#2 /wp-content/plugins/event-espresso-core-reg/core/services/bootstrap/BootstrapCo in /wp-content/plugins/event-espresso-core-reg/core/services/loaders/ClassInterfaceCache.php on line 91
[17-May-2022 10:32:03 UTC] PHP Fatal error: Uncaught EventEspresso\core\exceptions\InvalidAliasException: "EventEspresso\core\services\cache\CacheStorageInterface" can not be used as an alias because the "EventEspresso\core\services\cache\TransientCacheStorage" class does not extend or implement it. in /wp-content/plugins/event-espresso-core-reg/core/services/loaders/ClassInterfaceCache.php:91
Stack trace:
#0 /wp-content/plugins/event-espresso-core-reg/core/EE_Dependency_Map.core.php(1118): EventEspresso\core\services\loaders\ClassInterfaceCache->addAlias('EventEspresso\\c...', 'EventEspresso\\c...')
#1 /wp-content/plugins/event-espresso-core-reg/core/EE_Dependency_Map.core.php(113): EE_Dependency_Map->_register_core_aliases()
#2 /wp-content/plugins/event-espresso-core-reg/core/services/bootstrap/BootstrapCo in /wp-content/plugins/event-espresso-core-reg/core/services/loaders/ClassInterfaceCache.php on line 91
[17-May-2022 10:32:30 UTC] PHP Fatal error: Uncaught EventEspresso\core\exceptions\InvalidAliasException: "EventEspresso\core\services\cache\CacheStorageInterface" can not be used as an alias because the "EventEspresso\core\services\cache\TransientCacheStorage" class does not extend or implement it. in /wp-content/plugins/event-espresso-core-reg/core/services/loaders/ClassInterfaceCache.php:91
Stack trace:
#0 /wp-content/plugins/event-espresso-core-reg/core/EE_Dependency_Map.core.php(1118): EventEspresso\core\services\loaders\ClassInterfaceCache->addAlias('EventEspresso\\c...', 'EventEspresso\\c...')
#1 /wp-content/plugins/event-espresso-core-reg/core/EE_Dependency_Map.core.php(113): EE_Dependency_Map->_register_core_aliases()
#2 /wp-content/plugins/event-espresso-core-reg/core/services/bootstrap/BootstrapCo in /wp-content/plugins/event-espresso-core-reg/core/services/loaders/ClassInterfaceCache.php on line 91
|
|
spirometry
|
May 18, 2022 at 3:55 am
did you receive my response with the error code?
|
|
spirometry
|
May 18, 2022 at 3:58 am
The reason I ask is because when I try to post the error code to you again (I can’t see it in my thread) I am getting an error message saying ERROR: duplicate reply detected; it looks as though youve already said that!
|
|
Tony
|
May 18, 2022 at 5:25 am
Hi there,
Yes, I can see your reply. It was flagged for review due to the amount of code within a single post, I’ve now removed your sites patch from the post and approved it so it displays here.
The error you are getting means there are missing file from your EE install.
You mentioned they reinstalled Event Espresso, do you know how exactly?
Here are the steps I would take:
1. Download the latest version of EE4 from your account page
—
2. On the site go to Dashboard -> Plugins -> Add new.
Click ‘Upload plugin’ at the top.
Select the .zip file you just downloaded from from above by clicking the ‘Choose File’ option and finding it on your machine.
Click Install now.
Here is how it looks on my site: https://monosnap.com/file/J5JHkBBEIsFrriPAsLJSlYQIxQvjLd
—
3. WordPress should show a message showing a version already exists and ask if you want to replace it, so you should see something like this:
https://monosnap.com/file/SSOM2p7kGqHAusijFmC8z61pMgS8xy
If you see that, click ‘Replace current with uploaded’.
That will replace the current files on your site with the let’s ‘clean’ version.
If you don’t see the above, take a screenshot of what you see and add it here so I can take a look:
https://eventespresso.com/wiki/troubleshooting-checklist/#screenshots
(Note – do not use FTP or any other ‘manual’ method to try and fix this as that is the usual cause of the above error)
|
|
spirometry
|
May 18, 2022 at 11:39 am
This reply has been marked as private.
|
|
Tony
|
May 18, 2022 at 1:25 pm
No, your event data is stored within the database, not the plugin files.
To be 100% sure, I recommend creating a database backup before your walk through the above steps. EE does not delete the data within the database unless you chose an option within the Maintenance section of EE to reset the data, re-installing or deleting Event Espresso does not remove data.
|
|
spirometry
|
May 23, 2022 at 11:50 pm
So our IT rep has tried uploading the new plugin file through the WordPress backend but they encountered an error:
An error has occurred: The url given for EE assets is invalid. The URL provided was: “https://spirometryeducation.com.au/wp-content/plugins/event-espresso-core-reg 2/assets/dist/”. This usually happens when another plugin or theme on a site is using the :plugins_url” filter or has an invalid url set for the “WP_PLUGIN_URL” constant. Registry – registerManifestFIle-668
They are not getting the window screen where we are asked to replace the plugin files. Is it possible that this could also be caused by the outdated plugins and theme versions?
|
|
spirometry
|
May 23, 2022 at 11:51 pm
what do you suggest our next action should be?
|
|
Tony
|
May 24, 2022 at 2:49 am
/event-espresso-core-reg 2/ is not a valid directory name for WordPress, it should no contain spaces.
You mentioned the IT rep uploaded EE through the backend, however, WordPress would never name a directory with ‘ 2’ on the end, so did they upload the plugin through the dashboard or via FTP?
The way to fix both of your current errors is to use the latest version uploaded through the WordPress dashboard, both of the issues mentioned usually happen when people uploaded the plugin via FTP and files are skipped or they have incorrectly renamed the directory.
The directory name latest version needs to be fixed so it is back to event-espresso-core-reg, your IT rep should be able to do that for you.
|
