Yesterday both the site and dashboard has been down for a long time when trying to restore a backup through manage WP.
We spent all evening (5pm to after midnight) trying to restore the backup "manually". This morning only we can say that the backup has been restored. Apparently the fatal error comes through Toolset forms. See the message we have received. This plugin apparently completely ignore WordPress best practices and therefore it went completely wrong during the backup/recovery process.
-----------
Message:
Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, Toolset Forms.
First, visit your website (hidden link) and check for any visible issues. Next, visit the page where the error was caught (hidden link) and check for any visible issues.
Please contact your host for assistance with investigating this issue further.
If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.
To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.
When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.8
Current theme: Astra (version 3.6.7)
Current plugin: Toolset Forms (version 2.6.10)
PHP version 7.4.21
Error Details
=============
An error of type E_ERROR was caused in line 276 of the file /var/www/html/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/inc/autoloaded/interop/handler/woocommerce/fields.php. Error message: Uncaught Error: Call to a member function assign_post_type() on null in /var/www/html/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/inc/autoloaded/interop/handler/woocommerce/fields.php:276
Stack trace:
#0 /var/www/html/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/inc/autoloaded/interop/handler/woocommerce/fields.php(257): OTGS\Toolset\Common\Interop\Handler\WooCommerce\Fields->create_field_group()
#1 /var/www/html/wp-includes/class-wp-hook.php(303): OTGS\Toolset\Common\Interop\Handler\WooCommerce\Fields->autoregister_woocommerce_fields()
#2 /var/www/html/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters()
#3 /var/www/html/wp-includes/plugin.php(470): WP_Hook->do_action()
#4 /var/www/html/wp-settings.php(556): do_action()
#5 /var/www/html/wp-config.php(94): require_once('/var/www/html/w...')
#6 /var/www/html/wp-load.php(50): require_once('/var/www/html/w...')
#7 /var/www/html/wp-admin/admin-post.php(19): require_once('/var/www/html/w...')
#8 {main}
t
Thank you for contacting us and sorry to learn about the difficulty you had.
I've performed several tests on my website with activation and deactivate of different Toolset plugins, but couldn't reproduce this error.
The error message suggests that part of the code from Toolset Forms related to WooCommerce was executed when the WooCommerce's post type "Products" was not available on the website. But, in Toolset plugins, extreme care is taken to include conditional checks to only execute the code related to the third-party plugin, when that particular plugin is active.
I'm not familiar with manage WP, so can you please share the exact steps/process when you started to see the error?
Also, were you trying to restore a backup that had an older version of WordPress, WooCommerce, or Toolset plugins installed?
This information will help in reporting this matter to the development team for further investigation.
The exact steps/process when you started to see the error?
>> The site completely went down immediately after hitting "restore backup" through manage WP. After that we've received the email with the notification.
Were you trying to restore a backup that had an older version of WordPress, WooCommerce, or Toolset plugins installed?
>> No, we restored a website version of only a few days before with the exact same version of WordPress and WooCommerce. However, before restoring, we updated all new Toolset updates that were available. Could that cause the issue?
