NO BUG: Is-layout-flex does not work

Bugs
1

Browser: Chrome 139
OS: Windows
URL: https://staging.demayorquierosermochilera.com/seguro-viaje/seguro-viaje-embarazo/

After migrating to Bricks 2.0.1 display flex has been lost inside the post content and some elements appear to be aligned to the left (buttons, iframes and vertical images), as the rest of the text, instead of center.

The css element:

body .is-layout-flex {
    display: flex
;
}

is not appearing.

2.0.1 layout
2.0.1 layout800×585 66.4 KB

1.12.4 layout
1.12.4 layout941×508 57.8 KB

1.12.4 elements
1.12.4 elements1366×666 153 KB

2.0.1 elements
2.0.1 elements1366×674 174 KB

2

Hi Irene,
Thanks so much for your report!

Unfortunately, I don’t know exactly how to reproduce the problem.
Where does the content in this shortcode come from?

image
image1920×1200 214 KB

If this is the Gutenberg content: have you tried it with the post content element?

Best regards,
timmse

3

Hi @timmse,

I don’t know why is done that way (I’m just maintaining it) but the excerpt, the first banner and the content are all shortcodes. You can check the screenshot from the Bricks template:

shortcodes
shortcodes397×580 24.7 KB

I experience the errors on the content shortcode, which is inside a ‘content’ a ‘Container’, a ‘guttenburg content’ and a ‘column’ element, all of them with display flex set. But the buttons, the custom html and the columns elements added on the content using gutenberg are not displayed as flex.
To fix it I’ve had to apply the CSS properties directly on the style.css file:

body .is-layout-flex {
    display: flex;
}

Which I’m not sure it is the best way to do it and it wasn’t necessary on the previous version. That’s why I’ve thought it was a bug and I’ve opened the ticket.

Is it a bug or I should keep the properties on the style.css?

Thank you,

4

If you need access to the dashboard I can provide it.

5

Yes, please send temporary login credentials and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase.

6

The problem was caused by a custom shortcode and was easily solved by inserting the post content element instead of the shortcode to render the Gutenberg content.