Oxygen generates actual PHP and CSS from its visual component tree rather than storing a page-builder-specific format the way most builders do, which makes it powerful but also means a rendering failure is often a genuine code-level issue — a component referencing something deleted, a template’s condition scope no longer matching what it should, or Oxygen’s own generated-code cache serving something stale. That code-level nature cuts both ways: issues can be more precisely diagnosed once found, since you’re dealing with actual PHP and CSS rather than an opaque proprietary format, but finding the specific broken reference in the first place takes a more technical approach than most builders require.
Before you buy, one quick check
Read-only. In Oxygen, check whether the affected element shows an error or warning indicator in the component tree, which often points directly at what it’s referencing that no longer exists.
If it’s a template rather than a single page, check the template’s assigned conditions under Oxygen’s template settings, since a condition that no longer matches the intended pages is a common, specific cause worth confirming before ordering.
Checking your error log for a PHP notice or warning around the time the issue appeared is also worth doing if you have access to one, since Oxygen’s code-generation approach often surfaces genuine PHP-level warnings that other builders wouldn’t.
Oxygen builder rendering & template repair
An Oxygen-built component or template isn't rendering correctly. We isolate whether it's a caching, code-level, or template-scope issue and repair it.
- 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?
| An Oxygen component or template renders incorrectly or shows an error indicator | This fix covers it |
| The Oxygen editor itself won’t open | 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 Oxygen to another format | A conversion service, not this fix |
| The site’s generated CSS is bloated but nothing is actually broken | Builder-generated CSS bloat reduction |
What you are seeing
- A specific component or section failing to render or showing an error indicator
- A template applying to the wrong pages, or not applying where it should
- The editor showing a warning about a missing or deleted reference
- The issue appearing after deleting a global element the component depended on
- Correct rendering in one environment, such as staging, but not another
Common causes
- A component referencing a global element, class, or selector that’s since been deleted
- A template’s condition scope no longer matching the pages it’s meant to cover
- Oxygen’s generated code cache serving an outdated version after a structural change
- A PHP error in custom code added directly within an Oxygen component
- An environment mismatch, such as different active plugins between staging and live
What we do
- Reproduce the rendering issue and identify the specific component or template involved
- Trace any error or warning indicator back to what it’s actually referencing
- Determine whether the cause is a deleted reference, a scope mismatch, or stale cache
- Correct the underlying reference, condition, or code issue directly
- Regenerate Oxygen’s cached output and confirm correct rendering
- Check for the same referencing pattern elsewhere to rule out a wider issue
What is included
- The specific rendering issue identified and its root cause corrected
- Oxygen’s generated cache regenerated to confirm the fix
- A check for the same pattern causing issues elsewhere
- The pre-fix backup, kept for 30 days
Not included
- Rebuilding components or templates beyond restoring intended function
- Debugging custom PHP code unrelated to the specific rendering issue
- Fixing a different page builder’s components, even on the same site
- Ongoing monitoring for future structural changes elsewhere on the site
Questions about this fix
Does Oxygen being more code-based make this harder to fix than other builders?
Not necessarily harder, but it does mean the cause is more often a genuine code-level reference issue rather than a settings glitch, which changes how we approach the diagnosis.
Will I lose the component's design if a reference has to be corrected?
No — we correct what it's pointing at rather than rebuilding the component, so its design and settings stay intact.
Could this be caused by custom code I added myself?
Yes, that's one of the possibilities we check, and if that's the cause we'll show you exactly what's responsible so you understand it going forward.
Why does this only show on live and not staging, or vice versa?
Usually because the two environments have a genuine difference — different active plugins, different cached state, or a different PHP version — which we check as part of the diagnosis.
Will regenerating Oxygen's cache fix everything on its own?
Sometimes, if stale cache was the whole story, but if the underlying reference or condition is genuinely broken, regenerating alone just rebuilds the same broken result.
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.