lisa
(@contentiskey)
-if you have access to your webhosting account, you can try the following: find the plugins folder in your file manager area and rename it. renaming the plugins folder will deactivate all plugins and if the error is related to a plugin, you might be able to get inside the WP-Admin area to do further troubleshooting.
-if the backup copy was created by your webhosting vendor, contact the webhosting support team about instructions to restore the backup of your files and database.
-if the backup copy was created by a plugin, contact the plugin’s support team about instructions to restore the backup of your files and database.
Thank you I am muddling through with google searches to attempt to figure this all out. I did find the Plug in section on GoDaddy. I am not sure how to rename the folder. There is a back up someplace that does trigger each day thankfully.
I was able to remove the plug in section through Go Daddy. I now have part of my front page back up but still no access to WP and getting an HTTP 500 error that enzymediane.com is currently unable to handle this request.
lisa
(@contentiskey)
what did you remove?
are you able to restore your backup?
go daddy was able to get me in. So I am back in but i still have the plug in folder disabled. Is it better to try to use the back up or do i try to figure out how to add in each plug in again?
Go Daddy said it was the theme that was causing issues so they did change that theme. So now its all messed up.
I received the same error after an auto-update to Jetpack 11.8, which was couple of days ago. The way I was able to disable it was by renaming the Jetpack plugin directory, then reloading the admin interface. If you then go to the plugins page, you will see a message that WordPress has disabled the plugin due to an error. Now go back to the plugins directory and rename the Jetpack plugin directory to its original name. Returning to the plugins page will show the Jetpack plugin in a disabled state.
At this point I am going to wait for an update to the plugin instead of installing an older version.
If you are not running the Jetpack plugin, you can simply look through the plugins’ directory and check which plugin’s directory was most recently updated, then rename said directory. It is how I identified the Jetpack plugin as the culprit in my case.
I am running WP 6.1.1 on Linux.
