|
jmarken
|
March 25, 2023 at 10:37 am
For the second time this year, a routine update gave me a fatal error. I can’t remember all the hoops I had to jump through last time, but this time I went straight to WP recovery mode only to find the plugin completely missing. I could reinstall only the decaf version and there’s nowhere to put my license key.
Thankfully the site is working right now but I need the right version for updates and full capability.
|
|
Tony
|
March 25, 2023 at 3:49 pm
Hi there,
Unfortunately due to the sheer number of plugins, themes, configs, settings and various hosting available within the WordPress ecosystem, fatal errors are inevitable as we simply can not test against every possible combination/setup.
What we can do, is jump on those fatal errors when they come up and get a fix up as quickly as we can.
With this:
I could reinstall only the decaf version and there’s nowhere to put my license key.
Why only the decaf version?
Did you try to install the version from your account page (4.10.46.p)?
If so, what happened? (I’m trying to work out why you got a fatal so we can work through it)
Do you have the fatal error that was thrown?
|
|
jmarken
|
March 27, 2023 at 5:47 am
Yes, I downloaded the 4.10.46 version from your site and tried to install by “uploading plugin.” It said the plugin already existed. Do I have to deactivate and delete the Decaf version first? Will my data stay intact? (I just downloaded a back-up of the site, but of course reinstalling from that won’t solve the problem.)
Sorry, I didn’t think to screenshot the fatal error when it popped up, but it was during the process of updating. If I get it again I will capture it. Or if there is a tool I can use to find it let me know. Thanks for your response.
|
|
Tony
|
March 27, 2023 at 6:04 am
Deactivate Decaf (you don’t need to delete it just yet)
Then reinstall Event Espresso 4.10.46.p and click to replace the current version.
Will my data stay intact?
Yes, your EE data is stored within the database and WordPress does a relatively poor job of explaining what will happen when you delete a plugin. In short, it’s up to the plugin you are deleting to run a function and remove the data from the database when it’s deleted. WordPress provides a method for plugins to do that should they wish… however, I personally think it’s the wrong way to go about it as there are multiple valid reasons you may want just to delete a plugin and leave everything else in place.
So, EE does NOT delete your data on de-activation/delete. We DO have functions that can do that for you should you wish to remove the data but they don’t run automatically at all.
|
|
jmarken
|
March 27, 2023 at 6:26 am
I did as you said, deactivated decaf and tried to install, and I got the same message: Destination folder already exists. /home/dh_3mwriq/mainlyclay.com/wp-content/plugins/event-espresso-core-reg/
It didn’t give an option to replace current version. (I can send screenshot if you like.) I think I can reach that folder by FTP. Should I delete manually?
|
|
Tony
|
March 27, 2023 at 6:30 am
Which version of WordPress are you running? (It usually shows on the bottom right of the dashboard)
I think I can reach that folder by FTP. Should I delete manually?
If you are comfortable doing so then yes that’ll work too.
Then install 4.10.46.p through the dashboard (I do NOT recommend installing EE via FTP).
|
|
jmarken
|
March 27, 2023 at 6:34 am
WordPress 6.1.1. I’ll try deleting now and installing through the dashboard. Will let you know. Thanks.
|
|
jmarken
|
March 27, 2023 at 7:02 am
The folder will not delete. It just sits spinning. I will contact DreamHost support and see if they will do it…
|
|
Tony
|
March 27, 2023 at 7:16 am
Odd but that explains why WP didn’t offer to replace the directory for you.
|
|
jmarken
|
March 27, 2023 at 8:44 am
All is well! I was able to delete the folder by FTP, install and activate the newest version, and delete the decaf version. Data intact as you said. Keeping fingers crossed for the next update. Thanks for your help!
|
|
Tony
|
March 27, 2023 at 1:48 pm
Awesome, I’m glad it worked.
Any further issue just let us know.
|
