Page Builder Issues
A page builder can fail inside the editor while the public page still works, or the editor can save successfully while visitors see an old or broken layout. Identify which part is affected before changing plugins or templates.
Describe the problem
- Does the editor load, and can it open the affected page?
- Can you save changes, and does WordPress confirm the save?
- Does the problem appear on the public page, in the editor or both?
- Is every page affected or only one layout, widget or template?
Check for a cached or browser-specific result
- Open the public page in a private browser window.
- Clear the page builder’s generated files or CSS using its own maintenance tool where available.
- Clear the site and CDN cache once, then reload the page.
- Check the browser console and hosting logs for errors at the same time.
Review recent changes
Note any page-builder, add-on, theme, WordPress or PHP update made before the problem began. Component testing is safer on staging and should focus on the likely change rather than disabling unrelated site features. Submit a Fix Request if you want a developer to investigate the conflict.
Common questions
Frequently Asked Questions
Why does the editor look correct while the public page is broken?
The public page may be using cached or previously generated styles, or the theme may apply different front-end rules from the editor.
Why can I open other pages but not one specific page?
That page may contain a block, widget, template or saved data that triggers the problem. Record which section loads last and any browser or server error.
Should I clear every cache repeatedly?
No. Clear the relevant builder, site and CDN caches once after a known change, then investigate further if the same result returns.
What information helps diagnose a page-builder issue?
Provide the affected page, whether the editor or public view is involved, the last successful action, recent updates and any displayed or logged error.