Bricks assigns templates to pages using conditions — this archive, that post type, everywhere except this category — and when two templates are set up with overlapping conditions, Bricks has to pick one, sometimes inconsistently, which shows up as a page displaying the wrong layout, or switching between two different ones depending on how it’s loaded. This kind of conflict tends to surface gradually as a site accumulates more templates over time, rather than announcing itself the moment a new template is created, which is part of why it can go unnoticed for a while.
Before you buy, check for overlapping conditions
Read-only. Go to Bricks → Templates and check the condition set on each template that might reasonably apply to the affected page — its specific condition, its priority number if templates support one, and whether more than one template’s condition genuinely overlaps.
Finding two templates whose conditions both match the same page confirms the mechanism directly, and noting which two saves real diagnostic time.
Reloading the affected page a few times is also worth doing, since a genuine condition conflict often produces inconsistent results between loads rather than the same wrong template every time.
It’s also worth checking whether the affected page belongs to a custom post type or taxonomy with its own specific templates, since those tend to accumulate overlapping conditions faster than standard pages and posts do.
Bricks builder template conflict
Two of your Bricks templates are matching the same page or condition, and only one should be. We identify which templates conflict and correct the targeting.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| Two or more Bricks templates have conditions that both match the same page | This fix covers it |
| A single template displays incorrectly, no second template involved | A different, narrower Bricks display fix |
| The Bricks editor itself fails to load | A different, broader editor-loading diagnosis |
| Multiple unrelated page builders are active on the site | Multiple builders active – consolidation plan |
| Content is being converted away from Bricks to another format | A conversion service, not this fix |
What you are seeing
- A page showing the wrong template’s layout
- The displayed template switching inconsistently between page loads
- The problem appearing after creating a new template with a broad condition
- Certain pages affected while others with similar conditions display correctly
- No obvious edit to the affected page itself explaining the change
Common causes
- Two templates both set to match the same post type, category, or archive condition
- A newly created template’s condition unintentionally overlapping an existing one
- Template priority, where supported, not set to reflect which should actually win
- A condition based on a taxonomy or custom field that changed after the template was set up
- Cached template output serving a version generated before a condition change
What we do
- Identify every template whose condition could plausibly apply to the affected page
- Confirm which templates genuinely overlap versus which only appear to
- Determine the correct template for the page based on your actual intent
- Adjust conditions or priority so only the intended template applies
- Clear template-related caches to confirm the fix on the live page
- Check other pages using similar conditions for the same latent conflict
What is included
- The conflicting templates identified and corrected targeting established
- A check for the same latent conflict on other pages
- Cache clearing to confirm the fix holds on the live site
- The pre-fix backup, kept for 30 days
Not included
- Designing new templates beyond correcting which existing one applies where
- Fixing a different page builder’s template system, even on the same site
- Restructuring your entire template condition strategy beyond this conflict
- Ongoing monitoring for future template additions
Questions about this fix
How do I know which template is actually the correct one for that page?
We ask you directly if it's not obvious from context — resolving the conflict means picking a winner, and that's a decision about your site's design intent, not a technical one we'd make without you.
Will this happen again if I add a new template later?
It can, if the new template's condition also overlaps, though understanding this conflict once makes it much easier to spot the pattern yourself before it becomes a live problem.
Does Bricks support template priority the way some builders do?
It depends on your version and how conditions are configured — we check what's actually available in your setup rather than assuming a specific mechanism exists.
Could this be caching rather than a genuine template conflict?
It can look identical from the outside, which is why we check both — a cached page serving stale template output produces the same symptom as an actual unresolved conflict.
Will fixing this affect the templates on pages that already display correctly?
No — we scope the fix to the specific conflicting condition, leaving templates that are already resolving correctly untouched.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.