NO BUG: Builder Preview Not Loading Theme Styles/Fonts (Frontend Fine) – v1.12.4 – Template Glitch

Bugs
1

Browser: Chrome 110
OS: macOS /

Message:
Hi Bricks team,
*everything is updated

  • Bricks 1.12.4, Bricks Child Theme
  • Theme Style is assigned globally by condition (“Entire website”) – not by any “set as default” (there’s no such option in this version)
  • Custom fonts uploaded via Bricks > Custom Fonts

Issue:

  • Frontend is fine (correct fonts, styles, etc)
  • Bricks builder is NOT fine: Theme styles and fonts do not load in the builder preview (unstyled, fallback fonts, colors missing, etc)
  • This started after a template broke—not a Theme Style issue, but a TEMPLATE issue
  • Caches fully cleared (WP Rocket, browser, etc), tested in incognito, no effect
  • No custom code in child theme

Questions:

  1. Is this a known Bricks bug? (Builder preview NOT matching frontend after a template breaks)
  2. Does changing breakpoints mid-build cause template or preview bugs?
  3. What is the fix or workaround for this builder preview issue?

Thank you

2

Hi @erinreye707,

thanks for the descriptions, but I can’t seems to replicate the bug you are describing. Can you send temporary login credentials to your test/staging website and a link to this topic to help@bricksbuilder.io using the email address you used during the purchase, so we can take a look?

Thanks,
Matej

3

thank you,
did you switch to a mobile first breakpoint on a page that had been started as desktop first breakpoint then start building for a while? haha because that’s what i did.
OMG ALSO JUST SAW THAT THE FIRST HALF OF MY MESSAGE GOT CUT OFF OH NO LOL i emailed support thank you <3

but if you see this before i get an email back,
i deleted all my bricks pages and templates and am working on new pages now but still noticing little glitches. do you have any insight on the mobile first issue that happens if you switch it on a page that you started as desktop first breakpoint?

thank you<3

4

Hi,

I’m just updating this topic with “no bug”, since you figured it out, as replied over the email :slight_smile:

Thanks,
Matej