4.0.0 Beta 8: "Smushed" Navigation Inline on Single Post Layout; Displays Correctly on Page

Hiya! I use the same hero section across my entire site. On pages, the navigation inline element is spaced properly. When I copy the hero section to the single post layout, as part of the new Layout Builder, it becomes “smushed,” for lack of a better word. I’ve looked to see if the flexbox layout was switched, or if there is excess padding on the right to no avail.

Homepage:

Single Post Layout

Layout Builder

Hi @dzsigray,

Thanks for writing in. Would it be possible for you to share the URL? This might help us get a better idea of what might be going on there. Thanks!

Hey @alexander! I just dropped it in a secure note above since it’s a DEV site.

I took down the Maintenance Mode wall so you guys can access it without needing to log-in. I’ll leave it down for the time being.

Dylan

@dzsigray, thanks for sharing this. When you say you copied the hero section over to your single post layout, did you save it as a preset or template and then apply it to the first section, or did you just manually copy it over one piece at a time? I’m seeing that for some reason the menu on your single post page is missing the flex-direction, justify-content and align-items values in CSS that should give it the proper style. When I copy that over from the main page, everything works. Could you please review your settings on the single page and ensure you have everything setup exactly like the home page?

Thanks!

Hey @kory – That’s really interesting! I saved the home page hero section as a preset and then applied that to the section on the single post layout, checking the box to replace the content. What setting(s) on the single post page do I change to add those CSS attributes in?

Thanks!

Hey @dzsigray, we found a discrepancy here where the dynamic CSS output isn’t 100% the same with the Inline Navigation element when used in the Content Builder vs the Layout Builder. We’ll get that sorted out and let you know here when it’s fixed (should be for the next patch).

Oh great, @alexander! Glad that you found the issue.

Fixed for next patch!