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.
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.
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.