Skip Navigation

[Resolved] toolset blocks v1.3 fatal error

This support ticket is created 4 years, 3 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 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 4 replies, has 2 voices.

Last updated by jimP 4 years, 2 months ago.

Assisted by: Waqar.

Author
Posts
#1778173

I just updated from Toolset Blocks v1.2.2.1 to 1.3, and it crashed home pages on my multisite. I went back to 1.2.2.1 and all now works again. I'm currently running WP latest and Toolset plugins (Types/Access) latest. Error below. Please advise...Jim P.

Fatal error: Uncaught Error: Class 'Toolset_Relationship_Role' not found
in /home/jimpro7/public_html/envs.lclark.edu/wp-content/plugins/toolset-blocks/backend/Services/Bootstrap.php on line 125

Call stack:

OTGS\T\V\S\Bootstrap::initialize()
wp-content/plugins/toolset-blocks/application/controllers/main.php:92
WPV_Main::initialize_classes()
wp-includes/class-wp-hook.php:287
WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:311
WP_Hook::do_action()
wp-includes/plugin.php:478
do_action()
wp-content/plugins/toolset-blocks/vendor/toolset/toolset-common/bootstrap.php:107
Toolset_Common_Bootstrap::__construct()
wp-content/plugins/toolset-blocks/vendor/toolset/toolset-common/bootstrap.php:126
Toolset_Common_Bootstrap::get_instance()
wp-content/plugins/toolset-blocks/vendor/toolset/toolset-common/bootstrap.php:116
Toolset_Common_Bootstrap::getInstance()
wp-content/plugins/toolset-blocks/application/controllers/main.php:115
WPV_Main::initialize_user_editor()
wp-includes/class-wp-hook.php:287
WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:311
WP_Hook::do_action()
wp-includes/plugin.php:478
do_action()
wp-settings.php:524
require_once()
wp-config.php:105
require_once()
wp-load.php:37
require_once()
wp-blog-header.php:13
require()
index.php:17
#1778201

Hi,

Thank you for contacting us and I'd be happy to assist.

We've already reported this issue to the concerned team and it happens, when the "Relationships" migration wizard needs to run.

For now, I'll recommend the following steps:

1. Please deactivate all Toolset plugins except Toolset Types.

2. Update all Toolset plugins, but without activating them.

3. Next, please go to WP Admin -> Toolset -> Relationships and use the "Run the migration" button, to complete this migration.

After that when you'll activate Toolset Blocks or other plugins, you'll not see the same fatal error.

I hope this helps and please let me know if you need any further assistance around this.

regards,
Waqar

#1778863
Screen Shot 2020-09-16 at 7.16.35 AM.png

I followed your steps, but they did not fix the problem.

This is on a five-site multisite, where I discovered only one site has relationships. (I am not sure why those relationships are the old style, as I created them in spring 2020 with most recent Toolset plugins.) I ran the update relationships process, and all worked well.

I then re-activated Toolset plugins, all most recent versions, and got an equivalent error (below; includes error text for one subsite and error text for the root site). I then uninstalled Blocks 1.3, reinstalled 1.2.2.1, and the error was again fixed.

I have confirmed that the relationships on that one site successfully migrated; see attached image.

Below is error text...Jim P.

***

 Fatal error: Uncaught Exception: Could not make \OTGS\Toolset\Views\Controller\Shortcode\Resolver: Class \OTGS\Toolset\Views\Controller\Shortcode\Resolver does not exist
in /home/jimpro7/public_html/envs.lclark.edu/wp-content/plugins/toolset-blocks/vendor/toolset/toolset-common/lib/auryn/lib/Injector.php on line 412

Call stack:

OTGS\T\C\A\Injector::provisionInstance()
wp-content/plugins/toolset-blocks/vendor/toolset/toolset-common/lib/auryn/lib/Injector.php:372
OTGS\T\C\A\Injector::make()
wp-content/plugins/toolset-blocks/embedded/inc/classes/wpv-render-filters.class.php:68
WPV_Frontend_Render_Filters::pre_process_shortcodes()
wp-content/plugins/toolset-blocks/vendor/toolset/toolset-common/user-editors/editor/screen/beaver/frontend.php:62
Toolset_User_Editors_Editor_Screen_Beaver_Frontend::before_render_shortcodes()
wp-includes/class-wp-hook.php:287
WP_Hook::apply_filters()
wp-includes/plugin.php:206
apply_filters()
wp-content/plugins/bb-plugin/classes/class-fl-builder.php:1797
FLBuilder::render_content_by_id()
wp-content/plugins/bb-theme-builder/classes/class-fl-theme-builder-layout-renderer.php:437
FLThemeBuilderLayoutRenderer::render_content()
wp-content/plugins/bb-theme-builder/includes/content.php:3
include()
wp-includes/template-loader.php:106
require_once()
wp-blog-header.php:19
require()
index.php:17



Fatal error: Uncaught Exception: Could not make \OTGS\Toolset\Views\Controller\Shortcode\Resolver: Class \OTGS\Toolset\Views\Controller\Shortcode\Resolver does not exist
in /home/jimpro7/public_html/envs.lclark.edu/wp-content/plugins/toolset-blocks/vendor/toolset/toolset-common/lib/auryn/lib/Injector.php on line 412

Call stack:

OTGS\T\C\A\Injector::provisionInstance()
wp-content/plugins/toolset-blocks/vendor/toolset/toolset-common/lib/auryn/lib/Injector.php:372
OTGS\T\C\A\Injector::make()
wp-content/plugins/toolset-blocks/embedded/inc/classes/wpv-render-filters.class.php:68
WPV_Frontend_Render_Filters::pre_process_shortcodes()
wp-content/plugins/toolset-blocks/vendor/toolset/toolset-common/user-editors/editor/screen/beaver/frontend.php:62
Toolset_User_Editors_Editor_Screen_Beaver_Frontend::before_render_shortcodes()
wp-includes/class-wp-hook.php:287
WP_Hook::apply_filters()
wp-includes/plugin.php:206
apply_filters()
wp-content/plugins/bb-plugin/classes/class-fl-builder.php:1797
FLBuilder::render_content_by_id()
wp-content/plugins/bb-plugin/classes/class-fl-builder.php:1858
FLBuilder::render_content()
wp-includes/class-wp-hook.php:287
WP_Hook::apply_filters()
wp-includes/plugin.php:206
apply_filters()
wp-includes/post-template.php:253
the_content()
wp-content/themes/genesis/lib/structure/post.php:486
genesis_do_post_content()
wp-includes/class-wp-hook.php:287
WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:311
WP_Hook::do_action()
wp-includes/plugin.php:478
do_action()
wp-content/themes/genesis/lib/structure/loops.php:119
genesis_standard_loop()
wp-content/themes/genesis/lib/structure/loops.php:38
genesis_do_loop()
wp-includes/class-wp-hook.php:287
WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:311
WP_Hook::do_action()
wp-includes/plugin.php:478
do_action()
wp-content/themes/genesis/lib/framework.php:66
genesis()
wp-content/themes/genesis/page.php:15
include()
wp-includes/template-loader.php:106
require_once()
wp-blog-header.php:19
require()
index.php:17

#1779673

Hi Jim,

This second error that you shared has been reported to the concerned team as well and it is limited to the websites with the Beaver Builder.

A patch is available for this at this errata entry:
https://toolset.com/errata/fatal-php-error-on-sites-using-beaver-builder-after-updating-to-blocks-1-3/

You can expect the release with a fix for both these errors, very soon.

regards,
Waqar

#1799509

Blocks v1.3.1 seems to have fixed problem as you indicate!...thanks.