Grid Builder Visual Composer – Conflict

We offer an integration for Toolset with Visual Composer, but that’s only available for the paid Toolset.

As far this goes, also without the paid Toolset and no integration, the Visual Composer should not be broken by Types.

Can you show me in a short step by step description what I need to do to replicate the issue?
Then I can report this to the Developers and we can fix it eventually.

It is also good to know whether this used to work (what you describe) with previous Types versions

Thank you

Thank you for your answer.

The problem is more complicated, because the Grid Builder from Visual Composer does not work properly when turned on are also two plugins “Yoast SEO v3.9” and “Toolest Types v2.2.4.” Isolated plug any of them does not cause Fault Grid builder.
I do not know which module should be repaired.

Steps duplicate bug:
1. Install and enable the following plugins
-‘Toolest Types v2.2.4’
-‘Yoast SEO v3.9’
-‘Visual Composer v4.12.1’
2. Enter in the menu “Visual Composer – Grid Builder”
-Add New item
-In any place, click the icon ‘plus’ and add a block ‘Post Title’ or ‘Post Date”.
(First bug: This should open the editing window, instead of just adding an element)
-Next “Edit Post Title” to change anything and try to save the button ‘Save changes’
Unfortunately, the save button does not work.

I have Visual Composer 5.0 and Types (latest), this works fine together.

Then I activate the SEO Plugin and can not add any blocks anymore.
Several JS errors happen in the console.

When I disable Types half the issues are gone.

It means, there are still fatal JS errors, coming from the SEO plugin, but the issue that you can not add or edit the block is gone.

Now, the issue can be due to the fatal JS error happening on SEO/Visual Composer.

Sure is, Types and Visual Composer together work just fine.
As soon we bring in SEO, JS errors happen.

Without SEO, no JS errors at all happen.

So I would suggest to contact the SEO Plugin authors because the JS errors are related to that Plugin.
If then the issue still happens, we will try to fix eventually on our part as well, but I can not spot errors coming from Types, instead I see errors from the SEO plugin making it impossible for the plugins to work together.

We are open to work together as well, and I will inform our Developers on this issue here too, so we can already have a look at this.

Thank you “Beda” for your help.
I reported the problem to the author of the plug “Yoast SEO”.
https://github.com/Yoast/wordpress-seo/issues/6212

As you probably know, both plugs are very popular so the problem should be resolved.

Yes, I agree with you, and I also informed our Developers in regard.

We will analyse this.

Hi @bedas, @lgustaw

I’m trying to figure out is it VC’s issue. It seems that VC enqueue vc_vendor_yoast_js (on each post_type, I’m not sure) with dependency yoast-seo-post-scraper. From other side, Yoast SEO doesn’t load scripts when their metabox is hidden (for some post_type). It’s reason for error, because VC loads only post-scraper without other Yoast scripts.

You can see more info at https://github.com/Yoast/wordpress-seo/issues/6219
Can you try to remove array( 'yoast-seo-post-scraper' ) from function enqueueJs()? And test again everything.

The issue is not on Types.
https://github.com/Yoast/wordpress-seo/issues/6219

This is the correct fix and applying it works.

It needs to be passed to Visual Composer Authors, we (and eventually someone of YOAST) will do this.

hi there
anyone can help me ?
i have pinthis them and it dosent support visual composer any version can i do somthing
this them support my them ? i really need it

this is my site ???? ???