[Gelöst] WPBakery css not coming through to Content Template output pages

[Author]

Artikel

[Shane]

Hi Nick,

. A lot of the css is coming from the WPBakery builder automatically, e.g. the row spacing, responsive columns and of course any settings on the rows, columns and content blocks. So really it's impossible to get all this css and stick it in the Content Template's css section.

From my understanding of this you're saying that if you switch back to the content template without the WP Bakery Visual Builder your response columns will be lost and the settings in the row ?

I'm not able to replicate this because for the builder their settings is passed as shortcode parameters, for e.g in my test site i made a dotted line separator and this is what i generated.

[vc_row][vc_column][vc_separator color="black" style="dotted" border_width="5"][/vc_column][/vc_row]

From my testing you are still able to retain the settings even when the builder is not being used. Perhaps a test can be setup in the sandbox below.
versteckter Link

As you can see from my test link below.
versteckter Link

I have the content template in the shortcode mode and the frontend template is still displaying fine.

Thanks,
Shane

[nickT-2]

Hi Shane,

Thank you for the example, I can see how you've got it working using the Toolset custom css field.

In an ideal world we would be able to still use WPBakery and all of it's customisation settings.

Do you think that full compatibility with WPBakery is something the dev team can add to their future development? So that it works with the Auto assigned content templates. As a workaround for now I can assign these manually to my posts and products.

Thanks
Nick

[Shane]

Hi Nick,

I would suspect that this would be under review by the team but I cannot make no guarantees that they will make the change.

If there is enough reports of this particular issue affecting customers then it would definitely help to bump the priority of improving this but I still cannot make a guarantee of this being fully resolved.

UPDATE: An internal ticket for our developers have been created for this particular issue.
Thanks,
Shane

[Shane]

Hi Nick,

There has been a release of our Latest version of our plugins which should resolve this issue.

Please perform an update of your Toolset plugins and let me know if the issue still remains.

Thanks,
Shane