Skip Navigation

[Resolved] Upgrading to Toolset Access 2.8.6 causes a fatal error

This support ticket is created 4 years, 6 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: 

This topic contains 7 replies, has 4 voices.

Last updated by Robert 4 years, 6 months ago.

Assisted by: Shane.

Author
Posts
#1665701

While trying to upgrade to Toolset Access 2.8.6, I received the following fatal error:

Fatal error: Uncaught Error: Class 'Toolset_Post_Type_Exclude_List' not found in /home/atii/public_html/wp-content/plugins/types-access/application/controllers/permissions_post_types.php:209 Stack trace: #0 /home/atii/public_html/wp-includes/class-wp-hook.php(287): OTGS\Toolset\Access\Controllers\PermissionsPostTypes->registered_post_type_hook('payment_retry', Object(WP_Post_Type)) #1 /home/atii/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters('', Array) #2 /home/atii/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array) #3 /home/atii/public_html/wp-includes/post.php(1449): do_action('registered_post...', 'payment_retry', Object(WP_Post_Type)) #4 /home/atii/public_html/wp-content/plugins/woocommerce-subscriptions/includes/payment-retry/class-wcs-retry-post-store.php(45): register_post_type('payment_retry', Array) #5 /home/atii/public_html/wp-content/plugins/woocommerce-subscriptions/includes/payment-retry/class-wcs-retry-stores.php(67): WCS_Retry_Post_Store->init() #6 /home/atii/public_h in /home/atii/public_html/wp-content/plugins/types-access/application/controllers/permissions_post_types.php on line 209

"There has been a critical error on your website. Please check your site admin email inbox for instructions."

The only way to get out of this fatal error is to manually FTP into the website and delete the "types-access" plugin folder.

#1665799

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Robert,

Thank you for getting in touch.

We are currently aware of this issue and we're actively debugging to figure the cause.

I've added your ticket to our issues tracker and will be posting an update once there is any change.

Thanks,
Shane

#1665861

Hi,

exactly same issue here too after updating to Toolset Access 2.8.6.

Please keep me informed as well about any solution.

Thanks in advance

Michael

#1666719

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Guys,

Our development team has provided a patch for this.

Please go to the link below and follow the instructions in order to apply the patch.
https://toolset.com/errata/fatal-error-with-access-2-8-6-update-conflicting-with-some-other-plugins/

Thanks,
Shane

#1667563
2020-06-17 16_56_58-WordPress › Error.png

After installing and activating the latest version of Toolset Access v. 2.8.7, I still had the following fatal error:

Warning: include_once(/home/atii/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/lib/auryn/lib/injector.php): failed to open stream: No such file or directory in /home/atii/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/utility/autoloader.php on line 127

Warning: include_once(): Failed opening '/home/atii/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/lib/auryn/lib/injector.php' for inclusion (include_path='.:/opt/cpanel/ea-php73/root/usr/share/pear') in /home/atii/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/utility/autoloader.php on line 127

Fatal error: Uncaught Error: Class 'OTGS\Toolset\Common\Auryn\Injector' not found in /home/atii/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/utility/dic.php:19 Stack trace: #0 /home/atii/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/utility/dic.php(40): toolset_dic() #1 /home/atii/public_html/wp-includes/class-wp-hook.php(287): Toolset_Common_Bootstrap->{closure}(NULL) #2 /home/atii/public_html/wp-includes/plugin.php(206): WP_Hook->apply_filters(NULL, Array) #3 /home/atii/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/utility/dic.php(55): apply_filters('toolset_dic', NULL) #4 /home/atii/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/bootstrap.php(275): require_once('/home/atii/publ...') #5 /home/atii/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/bootstrap.php(91): Toolset_Common_Bootstrap->register_inc() #6 /home/atii/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-c in /home/atii/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/utility/dic.php on line 19
There has been a critical error on your website. Please check your site admin email inbox for instructions.

#1667907

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Robert

I suspect those errors occur because of a compatibility problem with another plugin (which triggers a call to code in our plugins that is not initialised yet).

Can you first disable all other plugins except for Toolset to confirm that the errors no longer occur, and then try re-enabling them to see if you can identify which causes the problem? Obviously this would be preferable on a staging site.

Then we can try to reproduce the issue.

#1668843

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Robert,

Were you able to perform the tests that Nigel had asked?

Please let me know as soon as you do this so that we can continue assisting here.

Thanks,
Shane

#1668995

So I upgraded to the latest version again and it crashed the site with the same fatal error. Then I disabled all of the plugins and re-installed Toolset Access. Then I re-enabled all of the other plugins one at a time. Interestingly enough, after enabling the final plugin there was still no fatal error. So at the moment it seems to be running fine.