Enfold fix
Avia Layout Builder Not Loading? Fix Enfold's Advanced Editor
You click Advanced Layout Editor and get a spinner, an empty canvas or a page that refuses to save. The page itself is almost always intact, because Enfold stores it as shortcodes in the database and the editor is only the window onto them. The job is finding what stopped the window from opening.
- post.php?post=214&action=edit 200 3.8 s
- JQMIGRATE: jQuery.fn.load() is deprecated
- Uncaught TypeError: a.indexOf is not a function
- at themes/enfold/.../assets/js/avia-builder.js:1
- admin-ajax.php avia_ajax_text_to_interface (pending)
What you are seeing
- The Advanced Layout Editor button does nothing, or the loader spins without end
- The builder canvas is blank on a page you know has content
- Element popups will not open, or open empty
- Update finishes and the page comes back as the older version
- One long page fails while short pages edit normally
Why it happens on Enfold
Most common first.
- 1
Enfold is older than the WordPress around it
The builder is a large piece of admin JavaScript written against the libraries WordPress shipped at the time. When WordPress updates itself and Enfold cannot, because no token was ever entered, the builder calls functions that are no longer there and stops at the first error. It is the usual cause on sites handed over years ago.
- 2
Another plugin's script failing on the edit screen
The builder shares the edit screen with every plugin that adds a meta box or a toolbar button. If one of their scripts throws an error first, Enfold's never finishes starting. Optimization plugins that minify or defer scripts for logged-in users, and CDN features that rewrite how scripts load, produce the same result.
- 3
A malformed shortcode in that one page
A builder page is a tree of av_ shortcodes. Pasted content, an interrupted save or a hand edit can leave a tag unclosed, and the builder cannot draw a tree with a branch missing. The tell is that only one page fails.
- 4
The save is larger than the server accepts
Long builder pages send a great many form fields in a single request. A low max_input_vars or post size limit cuts the request short without warning, and a web application firewall can reject it outright when it sees markup in the body. The page appears to save and returns unchanged.
- 5
Child theme files that shadow the builder
Child themes sometimes carry customized copies of builder elements. After a parent update the copy and the builder disagree about an element's options, and that element, or the whole canvas, fails to render.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Protect the page before you touch it
Take a full backup, or at least open the page's revisions and confirm a good one exists. If your host offers staging, do the rest there. Nothing below should delete content, but an editor that half loads can save half a page.
- 2
Open the console while the loader spins
On the page's edit screen press F12, choose the Console tab and reload. A red error names a file. If its path contains /plugins/, that plugin is the suspect. If it contains /themes/enfold/, the theme is out of date or incomplete.
- 3
Compare Enfold's version with WordPress
Check the version under Appearance, Themes against the current one on ThemeForest. If you are far behind, enter a personal token under Enfold, Theme Update and update. Without a token, download the theme from the ThemeForest account that bought it and replace the enfold folder over SFTP, renaming the old folder first so no retired files linger. Theme options live in the database and survive.
- 4
Take script optimizers out of the admin
Clear your caching plugin and switch off its JavaScript minify, combine and defer options for logged-in users. If the site runs behind Cloudflare, disable Rocket Loader for wp-admin. Still stuck? Deactivate plugins in halves on staging until the builder opens.
- 5
Repair the one page that will not open
If every other page edits normally, the fault is in this page's shortcodes. Restore the last revision that opened. Failing that, Enfold has a builder debug mode, switched on with a short snippet from Kriesi's documentation in the child theme's functions.php, which shows the raw shortcode beneath the canvas so an unclosed tag can be found.
- 6
Raise the limits if saves are cut short
Ask your host to raise max_input_vars and the PHP post size, and to check the firewall log for blocked requests to post.php at the moment you pressed Update. A page that saves after that was being truncated in transit.
Keep it from coming back
- Keep a verified token under Enfold, Theme Update so the theme moves with WordPress
- Test updates on staging, then open your longest builder page before going live
- Exclude wp-admin and logged-in users from script minification and deferral
- Keep custom builder elements out of the child theme unless someone owns their upkeep
The permanent fix
A faster Next.js build, with a CMS made for your business
If the builder breaks with most rounds of updates, the site is telling you its parts no longer move together: a theme on one schedule, WordPress on another and plugins on a third. A Next.js build with a custom CMS has no layout builder to load and no shortcode tree to corrupt. Your team edits fields made for your services, staff and locations, and each page is published as a static file.
| On Enfold today | On Next.js with a custom CMS | |
|---|---|---|
| What you keep updated | WordPress, the theme, its builder and every bundled plugin, all in step | Nothing on a schedule. There is no theme or plugin stack to fall out of step |
| How a page is served | Built from the database on each visit, through the theme and its builder | Built ahead of time and served as finished files from servers near the visitor |
| How you edit it | A general-purpose builder with every option the theme ships | A CMS built around what your business actually changes: services, prices, photos, posts |
| What can break it | An update to any one of those parts, or a license that lapses | A change someone makes on purpose, tested before it goes live |
Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.
Want this fixed on your Enfold site?
Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.
Which of these sounds like you? (pick any)
Frequently asked
Almost never. The layout is saved in the database as shortcodes, and the canvas is drawn from them each time you open the page. If the public page still displays correctly, the content is intact and the problem is the editor's scripts. Do not press Update while the canvas is blank.
One page failing points at that page's shortcode, not at the theme. An unclosed tag or pasted markup breaks the structure the builder tries to draw. Restore an earlier revision, or use the builder's debug mode to see the raw shortcode and repair it.
It can, when Enfold is several releases behind. WordPress updates itself and changes the script libraries the builder leans on, while a theme with no update token stays put. Bringing Enfold current usually restores the editor. Rolling WordPress back is a short-lived patch.
For a small text change, yes, with care. In debug mode the shortcode is editable as text, and a developer can change wording there without the canvas. For anything structural, fix the editor first. Hand-editing nested shortcodes is how one broken page becomes two.
Keep reading
- ServiceFixing WordPress PluginsOne bad plugin can take your whole site down. We fix plugin conflicts, fatal errors, and security holes fast — and build custom plugins when the off-the-shelf ones fall short.
- ServiceFixing Broken WebsitesSite down, hacked, or falling apart? We diagnose it fast, fix what's broken, and tell you straight how to keep it from happening again.