Bricks Troubleshooting Handbook: 10 Fixes

How to Use This Handbook

Bricks problems look worse than they are. A white screen or a page that lost its styles feels fatal, but nearly every issue below is one of three things: a plugin conflict, a stale cache, or a setting you didn’t know existed. That’s why this handbook starts with isolation, not with the problem list.

Before you read further, run fault isolation on any broken page:

1. Deactivate all plugins except Bricks (Plugins → Deactivate)
2. Switch the theme to a default like Twenty Twenty-Five
3. Clear every cache layer: page cache, CDN, and Bricks → Tools → Rebuild
4. Reload. If it’s fixed, re-enable plugins one by one until the culprit shows itself

This routine solves 80% of support-thread cases on its own. Each problem below follows the same shape: symptom → root cause → fix.

Editor Won’t Load (Blank Page)

Symptom: clicking “Edit with Bricks” gives a white screen; the builder never opens.

Root cause: a PHP fatal error while the builder loads. The usual suspects: a plugin hooking into the editor, a memory limit too low for the builder, or a corrupted Bricks cache.

The fix:

1. Enable WP_DEBUG in wp-config.php (define('WP_DEBUG', true);) and open wp-content/debug.log — the fatal error names the file and the function that broke
2. If the log says “Allowed memory size exhausted,” raise the limit: define('WP_MEMORY_LIMIT', '256M');
3. If a plugin is named, deactivate it — in wp-admin if it loads, via phpMyAdmin if not
4. Rebuild Bricks’ CSS (Bricks → Tools → Rebuild) and retry

Styles Missing on the Front End

Symptom: the page renders but looks like unstyled HTML — no layout, no colors.

Root cause: the visitor is served cached CSS — your caching plugin stored the pre-save stylesheet, or Bricks’ own cache still holds an older build.

The fix:

1. Clear your page cache plugin first (WP Rocket, LiteSpeed or Perfmatters)
2. Clear Bricks’ cache: Bricks → Settings → Cache → Clear
3. Purge the CDN cache (Cloudflare) if you use one
4. Confirm in an incognito window so local cache can’t fool you

Changes Not Showing After Update

Symptom: you save in the editor, and the front end looks identical.

Root cause: caching again — visitors get a copy from before the save — or you edited a template that isn’t the one the page uses.

The fix:

1. Clear all three layers: page cache, Bricks cache, CDN
2. Check the template: the template name shows at the top of the editor — confirm it’s the one that applies to this page
3. If the page uses a template with conditions (e.g., all posts), open Templates → Conditions and verify the page matches one of them

Query Loop Shows Nothing

Symptom: the Query Loop section renders empty — no posts, no cards.

Root cause: the query’s filters exclude everything, the post type has no published posts, or a dynamic data tag is malformed, leaving the card template blank.

The fix:

1. Open the Query Loop settings and check the post type and filters; set status to “published”
2. Confirm the post type has published posts (Posts screen)
3. Check dynamic data tags in the card template — {post_title}, {post_excerpt} — for missing braces
4. Remove all filters; if posts appear, add them back one by one

Images Break on Mobile

Symptom: images overflow the container, squish, or crop oddly on small screens.

Root cause: the container has a fixed width while the image keeps its intrinsic ratio — object-fit and aspect ratio were never set.

The fix:

1. On the image element, set object-fit to “cover” (CSS tab)
2. Give the container a fixed aspect ratio (e.g., 4:3) so it holds its shape
3. Switch to the mobile breakpoint in the editor (responsive icons) and override the width
4. For hero images, use a background image with background-size: cover instead of an <img> tag

Fonts Look Wrong

Symptom: text falls back to a system font, or the font swaps visibly mid-load (FOUT).

Root cause: the font is loaded from Google’s CDN and that request is slow or blocked; the browser falls back and swaps when — or if — the file arrives.

The fix:

1. Localize the font: Settings → Theme Styles → Fonts, add the font as a custom font with files hosted on your server
2. Preload the main font file (woff2) so it’s fetched early
3. Check the browser console for a 404 on the font file and fix the path
4. Set a fallback stack so the swap is graceful if the file still fails

Plugin Conflict Patterns

Two distinct patterns produce most plugin-related breakage.

Problem 7: Script collisions (jQuery and globals).

Symptom: a slider, accordion or lightbox stops working after a plugin update.

Root cause: two plugins load conflicting jQuery versions or both overwrite the same global object; the second one wins and breaks the first.

The fix:

1. Open the browser console — the error names the file and line
2. Deactivate the plugin named in the error, then the other script-heavy plugins one by one
3. Use Perfmatters’ Script Manager to disable the conflicting script only on pages that don’t need it — no global deactivation

Problem 8: Global CSS collisions.

Symptom: buttons, headings or spacing suddenly look different site-wide.

Root cause: a plugin injects a global stylesheet whose selectors override Bricks’ classes.

The fix:

1. Right-click the element → Inspect, find the selector winning in the Styles panel
2. Deactivate the plugin that owns that stylesheet to confirm
3. Scope the plugin’s CSS to its own pages, or disable it on the front end

When All Else Fails

Problem 9: fatal white screen after an update.

Root cause: an incompatible core, plugin or theme update; the site dies at load.

The fix: restore the last pre-update backup (UpdraftPlus → Restore). Then update on staging first next time — never production.

Problem 10: a rendering bug that survives everything.

Root cause: a subtle interaction you can’t isolate on production.

The fix: reproduce it on staging with all plugins off. If it still happens with only Bricks active, it’s a Bricks bug — report it to the official forum with your version, a screencast, and the exact steps.

Most problems above are classics every builder hits — the five Bricks pitfalls cover the avoidable ones in detail. And the best troubleshooting is the kind you never need: the weekly maintenance checklist catches stale caches, broken backups and bloated databases before they become a white screen.