Skip Navigation

[Resolved] Avada Fusion Builder column spacing

This thread is resolved. Here is a description of the problem and solution.

Problem: When I apply a 0px column spacing attribute in the Fusion Builder, it is not respected on the front-end of the site.

Solution: Apply the patch found in the erratum post below. A permanent fix will be included in a future release.

Relevant Documentation: https://toolset.com/errata/content-templates-built-with-fusion-builder-have-different-column-widths-than-pages-with-the-same-layout/

This support ticket is created 6 years, 4 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
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 16 replies, has 2 voices.

Last updated by Fabian 6 years, 3 months ago.

Assisted by: Christian Cox.

Author
Posts
#1078759
Screen Shot 2018-08-09 at 4.53.44 PM.png

This product seems to be displaying correctly, can you check?
hidden link

This Content Template includes some code that is breaking Fusion Builder:
hidden link

When I try to save the template with Fusion Builder active, I see an error message "Your page content could not be displayed as a Fusion Builder layout. Most likely that means there is some invalid markup or shortcode in it."

#1079523

Hi, christian. Now it works.

I never use Fusion Buider from the Toolsets editor, because if you add code, especially div tags, Fusion Builder goes crazy. I usually create the container and the columns and then in the toolsets editor I add the code I need.

Probably when you have edited with the Fusion Builder and saved the changes it has broken the code.

The important thing is that right now it seems to work. I'm going to try on the production website to see if it works properly, because I'm already implementing everything there.

I will also mount a test website to do more tests and if I see something, I will notify you.

Thanks for your help and time.