[Resolved] Fatal Error whenever a new version of Toolset Views is released

[Author]

Posts

[Jason Bajor]

With the latest versions of WordPress I get notified whenever a website is experiencing a technical issue. On about 5 occasions now, I am notified of a technical issue associated with Toolset. The website still loads normally, but when attempting to access the back-end, a Fatal Error page appears (see attached image). My website host is Flywheel. When reporting the issue to their technical support team, they say the following:

"It looks like there is a fatal error on the site. Fatal errors typically come from plugin/theme conflicts causing the site to go down. This could be anything from bad code or a plugin that needs to be updated. Here is a super handy article on how to resolve fatal errors - hidden link and we recommend having the developer of the site look into the issue. 🙂
We turned on wp-debug, and it looks like the errors are coming from the "types" plugin. Within the article above, it states "If the error mentions a function and displays a path to a plugin or theme, you can rename or move that plugin/theme folder via SFTP to disable it." Once it is renamed via SFTP you should be able to access the wp-admin to further troubleshoot the error. 🙂 "

I take the suggested steps by renaming the folder to disable the plugin. I can then access WordPress normally. I delete Types, then re-install it. After it re-installs, I access the Toolset settings and I always see there is a new version of Toolset Views available. I then update Views. The problem goes away completely until, seemingly, the next time Views is updated. Then this whole process starts over again.

[Beda]

That error will be resolved in the next release 3.3.9

I will notify you here when this will be released.

The issue only happens when Types (The Installer) fetches some updates from the remote repo.
So this error actually should appear only and always then when there are imminent updates to Toolset.

You can ignore it as it does not break functionality, and we will fix this in the next release of Types.
The error should not interrupt the functionality of the Plugin per se, it will just eventually appear in the logs

[Beda]

This is released with the latest Types update from today: Types 3.3.9

[Jason Bajor]

Hi Beda, I updated to 3.3.9. The error cropped up again today, and I cannot log into WordPress backend. Here is a portion of the e-mail from WordPress. Also, see attached screenshot when attempting to log into WordPress.

WordPress version 5.3.2
Current theme: NMHS (version 1.0)
Current plugin: Toolset Types (version 3.3.9)
PHP version 7.2.26-1+ubuntu16.04.1+deb.sury.org+1

Error Details
=============
An error of type E_ERROR was caused in line 6 of the file /www/wp-content/plugins/types/vendor/otgs/installer/includes/class-otgs-installer-source-factory.php. Error message: Uncaught Error: Call to undefined function WP_Filesystem() in /www/wp-content/plugins/types/vendor/otgs/installer/includes/class-otgs-installer-source-factory.php:6
Stack trace:
#0 /www/wp-content/plugins/types/vendor/otgs/installer/includes/upgrade/class-otgs-installer-upgrade-response.php(128): OTGS_Installer_Source_Factory->create()
#1 /www/wp-content/plugins/types/vendor/otgs/installer/includes/upgrade/class-otgs-installer-upgrade-response.php(63): OTGS_Installer_Upgrade_Response->append_site_key_to_download_url('hidden link...', '77iTfEw9km', 'toolset', 'hidden link...')
#2 /wordpress/wp-includes/class-wp-hook.php(290): OTGS_Installer_Upgrade_Response->modify_upgrade_response(Object(stdClass))
#3 /wordpress/wp-includes/plugin.php(206): WP_Hook->apply_filters(Object(stdClass), Array)
#4 /wordpress/wp-includes/option.php(1832): apply_filters('pre_set_site_tr...', Object(stdClass), 'update_plugins')
#5 /www/wp-content/plugins/widgetize-pages-light/include/otw_components/otw_factory/otw_factory.class

[Beda]

This is the notorious walk of shame 🙁 - I apologise for the issues experienced.

Toolset Types promised and stated to include the Installer Fix, but it did not.
Then it promised it again, and again it did not.

However, this last release includes fixes.
I've personally confirmed to not see the error anymore now that the latest updates where triggered.

I apologise this mess. It should be good now and not generate issues anymore.

[Jason Bajor]

Thank you for the info, Beda. Much appreciated.