|
chrisaustin
|
December 8, 2016 at 5:34 am
Hi… I am currently unable to log into my WP dashboard because of an error that seems to be associated with an EE4 add on. Upon entering my credentials I get the following message…
Fatal error: Uncaught exception ‘EE_Error’ with message ‘Hooked in model extension ‘EEME_Person_Event’ too late! The model Event has already been used! We know because the action AHEE__EEM_Event__construct__end has been fired’ in /home/edenfi69/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/plugin_api/db/EEME_Base.lib.php:78 Stack trace: #0 /home/edenfi69/public_html/wp-content/plugins/eea-people-addon/core/db_model_extensions/EEME_Person_Event.model_ext.php(29): EEME_Base->__construct() #1 /home/edenfi69/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/plugin_api/EE_Register_Model_Extensions.lib.php(70): EEME_Person_Event->__construct() #2 /home/edenfi69/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/plugin_api/EE_Register_Addon.lib.php(321): EE_Register_Model_Extensions::register(‘People’, Array) #3 /home/edenfi69/public_html/wp-content/plugins/eea-people-addon/EE_People.class.php(163): EE_Register_Addon::register(‘People’, Array) #4 /home/edenfi69/publi in /home/edenfi69/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/plugin_api/db/EEME_Base.lib.php on line 78
|
|
Jason King
|
December 8, 2016 at 6:35 am
We’ve also gotten the same error message this morning. Can’t login and front end users are unable to proceed past adding an item to their cart. Our site is hosted through SiteGround and we received this email from them last night:
“Your website(s) listed below and hosted on your account were automatically updated to the newest version (4.7) of WordPress today. We kindly ask you to review your website and make sure there are no problems after the upgrade.”
I think there’s an option to restore a backup version through our host, but I’m not sure if that will fix the problem, or if this update is even related to the error message.
Thanks for any help!!
|
|
Tony
|
December 8, 2016 at 6:45 am
Hi there,
We will need to investigate this but the quick fix is to de-activate the EE4 People Add-on.
As you can not log into the site this will need to be done FTP or if you don’t have FTP access a file manager through your hosts admin area.
You need to navigate to /wp-content/plugins/
Find the directory called eea-people-addon and rename it to anything else, for example eea-people-addon-temp
This will de-active the people add-on which should prevent the above error.
If either of you are unsure of how to do this we can do it for you to get you up back up and running, if you prefer for us to do it for you you can send us FTP credentials using this form:
https://eventespresso.com/send-login-details/
|
|
Jason King
|
December 8, 2016 at 7:09 am
Thank you Tony. That quick fix seems to have gotten us around the error without any other issues. Please let us know if there’s a more permanent update we need to make.
Thanks again.
|
|
Tony
|
December 8, 2016 at 7:18 am
Great, I’m glad you’re back up and running.
Can you confirm if you have the latest version of EE (currently 4.9.22.p) and the People Add-on installed? (Currently 1.0.5.p)
Also are you using WPML on the site?
Note – once the plugin has been de-activated you can rename that directory back to the original. The plugin should not re-activate as you would normally need to do that through the plugins menu but it means your directories are named as expected.
|
|
chrisaustin
|
December 8, 2016 at 7:23 am
Hi Tony, thanks for this – Like Jason deactivating the EE4 People Plugin has allowed me to access my dashboard again. For info, I currently have EE4 v 4.9.4.p installed, and EE4 People 1.0.5.p. Regards, Chris
|
|
Jason King
|
December 8, 2016 at 7:35 am
We’re on EE 4.9.8.p
People Add-on 1.0.5.p
Not using WPML
|
|
Tony
|
December 8, 2016 at 8:28 am
Hi guys,
I did some investigating into this and the fix is to update to the latest version of Event Espresso.
4.7 changed how a WP core hook EE uses was fired, we accounted for this in EE 4.9.21 but as you are both using old versions neither have the updated code.
So if you update EE to version 4.9.22+ and re-activate the people add-on you should have no issues.
|
