This thread is resolved. Here is a description of the problem and solution.
Problem:
The issue here is that the user is getting a Fatal error on update, specifically an error like this.
Fatal error: Uncaught Error: Class 'OTGS\Toolset\Maps\Model\Shortcode\Distance\ConditionalDisplay' not found
Solution:
This normally occurs when the plugin is updated but your server times out while the update is running.
What happens is that your plugin is partially updated.
To resolve this you can manually perform the update by downloading the plugin from the link below and uploading it to your website . https://toolset.com/account/downloads/
Just tried to update a test site of the 3 Toolset Plugins we use, these being - Toolset Types, Maps & Views.
On doing so we received the below email, on inspection the site was broken and we couldn't access the site at all.
Fortunately we can roll back to a previous version stored on our server.
Any idea why this is happening?
--------
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 Types.
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.
Could you follow the instructions int he link below to enable the wordpress debugging so that I can know exactly what is causing this issue. hidden link
I have never used cPanel...servers are not my strong point hence we have a dedicated, totally supported host Flywheel, worth the extra bucks so we get them to sort things if they go wrong...which they never have to be fair.
I'll need another option for this, I'm not about to start trying to work out how, where and what to do with cPanel I'm afraid.
On updating I get a summery screen and it had the following:
Warning: include_once(/www/wp-content/plugins/toolset-maps/application/models/shortcode/distance/conditionaldisplay.php): failed to open stream: No such file or directory in /www/wp-content/plugins/wp-views/vendor/toolset/toolset-common/utility/autoloader.php on line 127 Warning: include_once(): Failed opening '/www/wp-content/plugins/toolset-maps/application/models/shortcode/distance/conditionaldisplay.php' for inclusion (include_path='.:/usr/share/php') in /www/wp-content/plugins/wp-views/vendor/toolset/toolset-common/utility/autoloader.php on line 127 Fatal error: Uncaught Error: Class 'OTGS\Toolset\Maps\Model\Shortcode\Distance\ConditionalDisplay' not found in /www/wp-content/plugins/toolset-maps/includes/toolset-maps-shortcode-generator.php:147 Stack trace: #0 /www/wp-content/plugins/toolset-maps/includes/toolset-maps-shortcode-generator.php(119): Toolset_Maps_Shortcode_Generator->get_fields_expected_attributes() #1 /wordpress/wp-includes/class-wp-hook.php(288): Toolset_Maps_Shortcode_Generator->register_assets('') #2 /wordpress/wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters(NULL, Array) #3 /wordpress/wp-includes/plugin.php(478): WP_Hook->do_action(Array) #4 /wordpress/wp-settings.php(548): do_action('wp_loaded') #5 /www/wp-config.php(100): require_once('/wordpress/wp-s...') #6 /wordpress/wp-config.php(5): require('/www/wp-config....') #7 /wordpress/wp-load.php(37): require_once('/wordpress/wp-c...') #8 /wordpress/wp-blog-header.php(13): require_once('/wordpress/wp-l...') #9 /www/index.php(17): require('/wordpress/wp-b...') #10 {main} thrown in /www/wp-content/plugins/toolset-maps/includes/toolset-maps-shortcode-generator.php on line 147
But then when I refreshed again the site seems fine.
So something went wrong. Toolset Map updated first and this warning appeared.
Types second and then Views updated last.
Any ideas?
Based on what I see here the problem seems to be that the connection timed out when you are trying to update.
This caused the files to be partially updated. In a case like this a manual update of the plugins would resolve the issue or trying to update the plugins one by one.
There should be no cause for concerns here. Are you still getting the errors after you've performed the update successfully ?