[Resolved] Toolset Blocks is causing Editor Issues

[Author]

Posts

[philipS-3]

Hey guys,

the latest version of Toolset Blocks is causing conflict with editors in other plugins, such as for example my newsletter plugin Fluent CRM. The moment I update, the Block Editor in Fluent CRM throws an error saying "This block has encountered an error and cannot be previewed." - this applies to pretty much all standard content blocks, whether paragraph, image or headline.

If I go back to 1.6.17, it works fine.

I tested the conflict with a brand new install just with Toolset & Fluent CRM to ensure that there's no other issue and could replicate the issue.

[Minesh]

Hello. Thank you for contacting the Toolset support.

That is strange.

Here is a sandbox site and you can auto-login to it using the following link:
- hidden link

Can you please setup a test and send me exact steps in order to reproduce the issue. You are welcome to install the required plugins/theme..

[philipS-3]

Hey there,

I just used your sandbox and indeed, if you just activate Blocks on a fresh install, the issue does not appear. I now activated also Toolset Maps, Forms and Access and now the issue is also visible in the Sandbox environment . Simply go in Fluent CRM to Email Templates and then create a new one - once you click in the editor to edit the text or add another block element, the error will show, as you can see in my screenshot as well.

Kind regards, Philip

[Minesh]

Ok I can see the issue when Toolset form's plugin is active.

We do not have any official integration with "FluentCRM - Marketing Automation For WordPress" plugin and I do see few JS errors on browser's console when I try to create new email template from the FluentCRM.

Can you please get in touch with FluentCRM support and check with them and ensure they are loading all the scripts at right time and if they confirm I'm happy to escalate this in front of our next level support.

[philipS-3]

Dear Minesh,

the JS errors are caused by Toolset. If I just run FluentCRM I don't have any errors! You can test it in your sandbox simply by deactivating Toolset.

I run more than 100 plugins on my side and none is causing the issue. The moment I activate Toolset, the errors appear. So the issue is not with their plugin but with yours, because FluentCRM is not conflicting with any other plugin.

Please escalate this to the next level of support so this can be investigated.

Kind regards, Philip

[Minesh]

I've escalated the issue in front of our next level support. Please hold on until further updates.

I'll get in touch with you as soon as I've any update on it.

[Minesh]

I've good news for you.

Our Devs shared the following workaround that you can use to fix the issue and the official hotfix will be provided with the next future releae of Toolset Forms plugin:

add_action( 'admin_enqueue_scripts', function() {
	if ( isset( $_GET['page'] ) && 'fluentcrm-admin' === $_GET['page'] ) {
		wp_dequeue_script( 'cred_settings' );
		wp_dequeue_script( 'cred_cred_post_dev' );
	}
}, 2 );

[philipS-3]

Dear Minesh,

thanks for the code, it indeed resolved the issue for the Forms plugin. Unfortately, I am facing the same issue with the Blocks plugin as well! However, in my test env. with just Fluent CRM and the Toolset Plugins and the code from above it works fine. On my live site it throws the same error the moment I activate the Blocks plugin - I run a lot more plugins on my live site, but the moment I deactivate the Blocks plugin the error goes away, so it's clearly still related.

Any idea if code similar to the one in the Forms plugin is also present in the Blocks plugin, which cause the error on my live environment and be triggered by a combination with other plugins?

Have a great start into 2025.

Kind regards, Philip

[Minesh]

Happy New Year and wishing you the greatest of year 2025 ahead!!

You must be using optimization plugins and here is the Doc that shows what files you have to exclude:
=> https://toolset.com/faq/how-to-use-optimization-plugins-with-toolset/

Can you please try to exlude those files and check if that helkps you to resolve your issue.

Please check the following related ticket:
=> https://toolset.com/forums/topic/split-filtering-views-for-specific-pages/page/2/#post-2766382