[Resolved] Toolset interfere with BeaverBuilder page builder

[Author]

Posts

[geneS]

Tell us what you are trying to do?
when Toolset plugin active, it added a (+) on beaver builder text field which should be hidden, because Toolset added this feature that I don't want to use.

Is there any documentation that you are following?
I have enclosed the screen shot with toolset active and not active inside beaver builder workflow. Notice when toolset is active, it display a bunch of keywords or whatever around the screen.

Is there a similar example that we can see?
We didn't see this issue before, it must be a new feature Toolset added that should be disabled if Customer don't want this feature
What is the link to your site?
hidden link

[Minesh]

Hello. Thank you for contacting the Toolset support.

This is a known issue to us and already reported in front of our Devs.

As a workaround - what if you try to use the following code that should help you to fix the issue.

You can add the following code to "Custom Code" section offered by Toolset:
=> https://toolset.com/documentation/programmer-reference/adding-custom-code/using-toolset-to-add-custom-code/#adding-custom-php-code-using-toolset

function func_enqueue_missing_field_and_text_toolset_shortcodes_css() {
   
  if(!is_admin() and  (isset($_GET['fl_builder']) or isset($_GET['fl_builder_ui'])) ) {
       
     wp_enqueue_style('wp-jquery-ui-dialog',site_url().'/wp-includes/css/jquery-ui-dialog.css', array(), false, 'all');
     
      wp_enqueue_style( 'toolset-shortcode-css',plugins_url().'/cred-frontend-editor/vendor/toolset/toolset-common/res/css/toolset-shortcode.css', array(), false, 'all');
     
  }
}
add_action( 'wp_enqueue_scripts', 'func_enqueue_missing_field_and_text_toolset_shortcodes_css');

[geneS]

Thank you for the workaround.. and the css enqueue works. However, if we do not want ToolSet feature shows up at all.. is there a way to completely "hide"/"remove" from beaver builder so (+) not showing and therefore cannot be clicked?

[Minesh]

In this change between versions 2.7.1.1 and 2.7.2 Beaver Builder removed (not dequeued: they deregistered) a key asset that we need to properly style our shortcodes dialogs.
- https://plugins.trac.wordpress.org/changeset/2960777/beaver-builder-lite-version/trunk/classes/class-fl-builder-compatibility.php

Apparently, given the comment on the line, it was to avoid some compatibility issues with other third party plugins.

I would kindly suggest you to explain this situation to the BB support team and request that they keep the style registered. Third parties, besides us, might be using it, and if it is causing conflicts with their UI then, well, their UI should just play nice with this core style.

The fix should rely on Beaver Builder side, please let them know and share feedback if they have with our findings.

[geneS]

I love developers relies on customer to talk to each plugin developer as if we know exactly what we are talking about. Developer A can't talk to Developer B from Company X because that is not our problem. it is their problem.. They need to fix it but we can't tell them because we are not the customer. Excellent customer support. On the other note.. you cannot control your own product to say.. oh.. if my customer don't want my features to exposed to other plugins.. well.. customer need to tell them not to accept our filter or actions.. Wouldn't it be nice to have my plugin that control our own features that enable/disable exposing to other plugins.. wow what a concept.. but no, not my feature, not my scope and not going to fix it. thanks

[Minesh]

Well - you may be misunderstood something here or could be different case.

I already shared the workaround that will help you to fix the issue.
- https://toolset.com/forums/topic/toolset-interfere-with-beaverbuilder-page-builder/#post-2708072

Regarding the fix, we can not apply fix to third-party plugin files, I hope that is understandable.

We encourage you to get in touch with BB support that will add your voice and they know that customer needs fix for X issue and you need that sooner. We can do that but if there is no customer asking the fix for the issue raise from our end - there are chances that it may be gone to archive or get less priority.

I hope this clears the picture and hopefully it will be win win situation for all of us who needs fix in third-party plugin file (in this case Beaver Builder).