- This topic has 20 replies, 5 voices, and was last updated 3 months ago by
.
-
Posts
-
Received this message moments ago…
The following plugins failed to update. If there was a fatal error in the update, the previously installed version has been restored.
– Weaver Xtreme Theme Support (from version 6.5.1 to 7.0) : https://wordpress.org/plugins/weaverx-theme-support/
Now when i go to the URL it shows the following error message…
There has been a critical error on this website.
My site is totally Elvis on Arrival.
There apparently was an issue with 7.0 of the Theme Support plugin. Not sure what, but it could possibly be an issue with what version of PHP your site is running.
For now, you may have to delete the old 6.x version, and reload the 7.0.1 version which really is just the same as the old 6.x version you had. This may require file access from you hosting company interface to delete the weaver-theme-support plugin directory.
I’ve had the 7.0 version tested on many websites with various other plugins without any issue. This leads me to believe it might be a PHP version issue.
Out of 50 Websites I manage, I have 10 that have a fatal error. I am thinking this something more people will be experienceing with the Theme Support Plugin.
Of the 1o sites with issues, have you recently updated them to WP7.0?
And if so, do you think any of them have a PHP less than 7.4?
There was only a 3 hour window with the error, so there shouldn’t be too many problems, and the replacement is simply the previous very stable version with the version updated so it doesn’t trigger the WP out of date warning.
@ROBIN – is there anything different about the 10 that triggered the error? Was it difficult to undo the new installation? And, as User asked, is it possible that you had an old version of PHP on those sites?Any chance you can pass along a sample of the Server Error messages you have got in full?
If possible, can you provide any relevant debug report too?
You may want to set your reply to Private…..
If you have access to your files and plugins via CPanel or FTP, I have regained access in such circumstances by remotely changing the name of the suspected problem file or plugin.
It normally only takes a few minutes while WP deals with Fatal Errors this creates and in doing so cancels in the effects of the errant file.
I know of no other way…
Or as WP says:
Sometimes it may be necessary to deactivate all plugins, but you can’t access the Administration Screens to do so. One of two methods are available to deactivate all plugins.
Use phpMyAdmin to deactivate all plugins.
- In the table wp_options, under the option_name column (field) find the active_plugins row
- Change the option_value field to: a:0:{}
Or reset your plugins folder via FTP or the file manager provided in your host’s control panel. This method preserves plugin options but requires plugins be manually reactivated.
- Via FTP or your host’s file manager, navigate to the wp-contents folder (directory)
- Via FTP or your host’s file manager, rename the folder “plugins” to “plugins.hold”
- Login to your WordPress administration plugins page (/wp-admin/plugins.php) – this will disable any plugin that is “missing”.
- Via FTP or your host’s file manager, rename “plugins.hold” back to “plugins”
Most of my sites, were able to be brought back by deactivating some larger plugins, updating Weaver and then reactivating the plugins. I used CPanel.
The site that gave me the most trouble is a newer site that I am currently working on. The page that gave me the fatal error still gives that error if I try to go into Elementor to work on it, That is fine, I am rebuilding that page and things are working. The weird part was I never received the Fatal Error email from WordPress on ANY of the sites that were effected. I am concerned that once I reactivate the plugins I need, that the page I am working on with Elementor will once again go into Fatal Error Status.
My thought pattern is if I keep going, the plugin that is the problem (don’t know which one yet) will have updated and it won’t be a problem any longer.
If I get the error again, I will be happy to pass on anything I can figure out.
Here are the Plugins I am using. The ones without the check mark are the ones I deativated. Maybe others can see if they are also using any of the same ones because I am fairly certain it is a problem with one of these. Fingers crossed it isn’t WooCommerce.
Backuply <i class=”fas fa-info-circle”></i> 1.5.3 <label class=”switch”><label class=”switch”><input id=”26_23496_backuply/backuply.php” class=”toggle_plugin_theme” name=”Backuply” type=”checkbox” /></label></label> Backuply Pro <i class=”fas fa-info-circle”></i> 1.5.3 <label class=”switch”><label class=”switch”><input id=”26_23496_backuply-pro/backuply-pro.php” class=”toggle_plugin_theme” name=”Backuply Pro” type=”checkbox” /></label></label> Classic Editor <i class=”fas fa-info-circle”></i> 1.7.0 <label class=”switch”><label class=”switch”><input id=”26_23496_classic-editor/classic-editor.php” class=”toggle_plugin_theme” checked=”checked” name=”Classic Editor” type=”checkbox” /></label></label> Classic Widgets <i class=”fas fa-info-circle”></i> 0.3 <label class=”switch”><label class=”switch”><input id=”26_23496_classic-widgets/classic-widgets.php” class=”toggle_plugin_theme” checked=”checked” name=”Classic Widgets” type=”checkbox” /></label></label> CookieAdmin – Cookie Consent Banner <i class=”fas fa-info-circle”></i> 1.2.0 <label class=”switch”><label class=”switch”><input id=”26_23496_cookieadmin/cookieadmin.php” class=”toggle_plugin_theme” name=”CookieAdmin – Cookie Consent Banner” type=”checkbox” /></label></label> CookieAdmin Pro <i class=”fas fa-info-circle”></i> 1.2.0 <label class=”switch”><label class=”switch”><input id=”26_23496_cookieadmin-pro/cookieadmin-pro.php” class=”toggle_plugin_theme” name=”CookieAdmin Pro” type=”checkbox” /></label></label> Elementor <i class=”fas fa-info-circle”></i> 4.1.1 <label class=”switch”><label class=”switch”><input id=”26_23496_elementor/elementor.php” class=”toggle_plugin_theme” checked=”checked” name=”Elementor” type=”checkbox” /></label></label> Form Maker Pro <i class=”fas fa-info-circle”></i> 2.15.22 <label class=”switch”><label class=”switch”><input id=”26_23496_form-maker/form-maker.php” class=”toggle_plugin_theme” checked=”checked” name=”Form Maker Pro” type=”checkbox” /></label></label> Kadence Mail <i class=”fas fa-info-circle”></i> 3.0.0 <label class=”switch”><label class=”switch”><input id=”26_23496_wp-smtp/wp-smtp.php” class=”toggle_plugin_theme” checked=”checked” name=”Kadence Mail” type=”checkbox” /></label></label> Loginizer <i class=”fas fa-info-circle”></i> 2.0.8 <label class=”switch”><input id=”26_23496_loginizer/loginizer.php” class=”toggle_plugin_theme” name=”Loginizer” type=”checkbox” /></label> loginizer Pro 2.0.8 <label class=”switch”><label class=”switch”><input id=”26_23496_loginizer-security/loginizer-security.php” class=”toggle_plugin_theme” name=”Loginizer Pro” type=”checkbox” /></label></label> MaxButtons 9.8.5 <label class=”switch”><label class=”switch”><input id=”26_23496_maxbuttons/maxbuttons.php” class=”toggle_plugin_theme” checked=”checked” name=”MaxButtons” type=”checkbox” /></label></label> Smush 4.1.0 <label class=”switch”><label class=”switch”><input id=”26_23496_wp-smushit/wp-smush.php” class=”toggle_plugin_theme” name=”Smush” type=”checkbox” /></label></label> SpeedyCache Pro 1.3.9 <label class=”switch”><label class=”switch”><input id=”26_23496_speedycache-pro/speedycache-pro.php” class=”toggle_plugin_theme” name=”SpeedyCache Pro” type=”checkbox” /></label></label> SpeedyCache 1.3.9 <label class=”switch”><label class=”switch”><input id=”26_23496_speedycache/speedycache.php” class=”toggle_plugin_theme” name=”SpeedyCache” type=”checkbox” /></label></label> Weaver Xtreme Plus 7.0.3 <label class=”switch”><label class=”switch”><input id=”26_23496_weaver-xtreme-plus/weaver_xplus.php” class=”toggle_plugin_theme” checked=”checked” name=”Weaver Xtreme Plus” type=”checkbox” /></label></label> Weaver Xtreme Theme Support 7.0.1 <label class=”switch”><label class=”switch”><input id=”26_23496_weaverx-theme-support/weaverx-ts.php” class=”toggle_plugin_theme” checked=”checked” name=”Weaver Xtreme Theme Support” type=”checkbox” /></label></label> WooCommerce 10.8.1 <label class=”switch”><label class=”switch”><input id=”26_23496_woocommerce/woocommerce.php” class=”toggle_plugin_theme” name=”WooCommerce” type=”checkbox” /></label></label> WooCommerce PayPal Payments 4.0.4 <label class=”switch”><label class=”switch”><input id=”26_23496_woocommerce-paypal-payments/woocommerce-paypal-payments.php” class=”toggle_plugin_theme” name=”WooCommerce PayPal Payments” type=”checkbox” /></label></label> WooPayments 10.8.0 <label class=”switch”><label class=”switch”><input id=”26_23496_woocommerce-payments/woocommerce-payments.php” class=”toggle_plugin_theme” name=”WooPayments” type=”checkbox” /></label></label> Hope this helps someone that is experiencing the awful Fatal Error screen.
Are you still having issues with the 7.0.1 version of the Theme Support plugin? The 7.0 version that broke things seemed to have a conflict with Woo and a couple of gallery plugins. The 7.0.1 is really the old reliable 6.x version but updated so it didn’t trigger PHP and not updated in too long.
And you might want to update your wp-config.php file to show errors instead of a screen-of-death ending.
define( ‘WP_DEBUG’, true );define( ‘WP_DEBUG_LOG’, true );define( ‘WP_DEBUG_DISPLAY’, true );I do think that some of these issues are not necessarily Weaver related, but PHP versions.Thank you
With help — InMotionHosting Support renamed the plugin and my site is restored.
No longer will I be updating any files just because WP.org says so.
I hope this didn’t end up breaking too many sites. One of the sites on my hosting company is my son’s professional business site, and it auto-updated to the broken version in the hour or two it was up. I still can’t really tell what what going on, but I’m convinced it is WP 7 and PHP version related.
I ended up having to completely restore the site from the daily backups my host provides.
The lesson is to disable autoupdates, and make it part of the routine to do manual updates every month or three.
Agreed on disabling auto-updates!
I also do full DB backups saved to Dropbox every 2 hours, as I post about 10 new posts throughout each day.
Fortunately I am in the same time zone as when developers tend to release updates, so I am normally working when they come in, and so I do another DB backup before updating. That way I don’t lose any work if an update messes the site.
My Host has always said they did daily backups, but on April 22, they wrote this to me during an exchange:
“We have nightly backup and keep 7 copies. However, we backup the entire server, not just your website. If you need restore, we have to restore the entire server.”
So it’s not just errors on my site that may cause loss and problems for me……
Which confirms that my UpdraftPlus backups to Dropbox are 100% a good idea. I have tested the backups before and when things have gone wrong in the past, and since all that can be done from WP Admin, they have been a quick and easy fixes. That said, I also have FTP and CPanel connections when WP fails totally which has been necessary in the past.
Hops this helps.
And yes, it may be worth asking your Host what their “daily backup” means in reality, as we don’t want to feel responsible for causing losses for countless other sites on the same server drive….. due to a WP plugin update.
I have a question.
If you use a plugin to backup your site, how can you restore it if the site is no longer accessible?
If it is a total fatal error which kills the site, I guess I cannot, which is why I make sure I am signed into both FTP and CPanel before updating.
But then again, I can’t recall such and event ever happening, perhaps because for each update, I am present and signed into admin already. Perhaps….
In truth, most problems with plugins don’t cause such catastrophic events, so it is rare event, but having a plugin not fully load because a file is missing and a warning generated, or it wipes out or changes all settings, or it adds unwanted features, are very common occurrences, and honestly, fixing them can be very time consuming and frustrating as typically I don’t keep a record of all the settings for each plugin.
Only last week one small plugin update did erase all the old settings and a large well know one was missing a file and so did not work.
As my main site is updated daily, I see no downside to having 2-hourly backup available, as there are so many opportunities for things to go horribly wrong, and the site users get very upset, very fast.
Hope this makes sense… 🙂
- You must be logged in to reply to this topic.