WIP: Critical CSS / Loop Rendering Bug in Bricks 2.2 RC2

marreiradigital · February 4, 2026, 4:50pm

Hello Bricks Team,

I would like to report a recurring rendering bug related to CSS loading and loops in Bricks Builder 2.2 RC2.

Environment

Bricks Builder: 2.2 RC2
WordPress: latest stable
Issue occurs on frontend only (editor renders correctly)

Description of the issue

Layouts inside any type of loop (Query Loop, dynamic data loops, etc.) intermittently break on the frontend.

Behavior observed:

In the Bricks editor, the layout renders correctly.
On the frontend, the same layout appears broken (styles missing, misaligned, or incorrect).
Regenerating CSS files sometimes fixes the loop layout, but then other non-loop pages break.
Switching Bricks > Settings > Performance > CSS Loading Method:
- Using Inline Styles fixes some loops, but not all.
- Switching back to External Files and regenerating CSS fixes some pages but breaks others.

This creates a visually inconsistent site where fixing one area breaks another.

Additional notes

Almost all other bugs we experienced in RC versions were resolved.
This CSS/loop issue is the only remaining blocking problem.
The problem appears related to CSS generation/cache invalidation when loops are involved.

Expected behavior

Consistent CSS rendering between editor and frontend.
CSS regeneration should not cause layout regressions across unrelated pages.
Loops should not behave differently from static layouts regarding CSS output.

Please let me know if you need:

A minimal reproduction
Debug logs
Temporary access to a staging site

Thank you for your work and support.

Best regards,

Paulo Marreira
WordPress Developer

Edit: This problem has been happening since the first RC.

MattHias · February 4, 2026, 5:35pm

Are you absolutely sure it’s not just a simple CSS syntax error in any of your rules?
On a small mistake, like a missing closing bracket on a CSS function like rgb(), clamp() etc, the browser will stop rendering the whole rest of the CSS.

In the builder, that might not be noticeable since the CSS is loaded in smaller chunks and different order. But in frontend, CSS is read from large files, and a single issue at the top kills all the remaining CSS.

Please share the (frontend) URL for investigation.

d19dotca · February 4, 2026, 5:36pm

I think I’m seeing the same thing but never noticed until RC2. Loads fine in the editor but not the frontend. Regenerating the external files didn’t solve it, but if I switch to inline CSS then everything appears fine again. This affects loops for me where I set them to load as grid, and using external files will show them on the frontend as flex instead. If I switch to inline styles then it loads perfectly fine on the frontend.

What it should look like (which it does in RC2 only if using inline styles):