[Resolved] Row Width issue using DIVI builder in Content Template

[Author]

Posts

[jimH-3]

I am trying to: get the contents of the page to be the full width of the content area. If you inspect the page, you will see that the regular sections with row do not take up the whole space available.

Link to a page where the issue can be seen: hidden link

I expected to see: I explained how things should work with divi on the page that was made in a content template, using the page builder.

Instead, I got: Explained how margins are not correct.

[Beda]

Toolset Views or Layouts, it does not matter which, will replace the_content() of your Theme.

Hence, "FULL WIDTH SECTION - THIS SHOULD GO FROM SCREEN EDGE TO EDGE" is only true to the margin of the the_content() which is defined by the Theme.

It is hence expected that this Row will not be from screen edge to screen edge.
It would break the design in the Front end.

[jimH-3]

Is there away to get it to at least go as wide as the content on any other page that is developed with the divi builder?

Thanks, Darin

[jimH-3]

.et_pb_row.et_pb_row_fullwidth, .et_pb_specialty_fullwidth>.et_pb_row {
width: 100% !important;
max-width: 100% !important;
}

The above CSS fixes the issue. I can apply this just to the content template I'm on. By going to the over all Divi builders settings menu from within the template I'm on. This way only the page that has the template on it, is effected and the rest of the site is fine.

I see that the row is set to 80% by Divi on the other pages, but 80% does not work on wp-types content template.

Unless you have a more elegant solution, you may close this ticket.

Thanks, Darin

[Beda]

DIVI uses different templates for posts or pages.
So on a page a fullwidth is wider than a on a post (they usually have the sidebars)

A full width row in a post looks exactly the same as a full width row in a post styled with a Content Template.

We also added options when DIVI is active, in the Content Template edit screen.
There you can change the main layout settings of DIVI, as well.

In native vanilla settings, both outputs look the same, thru Content Template or DIVI directly.

Eventually you use another layout setting(s) than the native one?