You press "Avada Builder" or "Live" on a page and get an endless loading circle, a blank white panel, or no builder button at all. Sometimes visitors see raw codes like [fusion_builder_container] instead of the design. Avada is the best-selling theme on ThemeForest, and it is really three parts that must stay in step: the theme, the Avada Core plugin and the Avada Builder plugin. Most editor failures come from those parts drifting apart, from server limits, or from a background request being cut off. Visitors may still see the site normally. Below is a rebuilt example (not a real client), two checks, and the fix for each cause.
In the dashboard open Avada > Status (called System Status in older versions). It lists the theme, Avada Core and Avada Builder versions and the server's PHP settings, and marks anything below Avada's minimums in red. Also look at the top of the dashboard for a notice that Avada Core or Avada Builder "needs to be updated", and at Plugins to confirm both plugins are active.
On a computer, open the stuck editor, press F12 (or right-click and choose Inspect), open the Console tab and reload. Read the first red line and the file name next to it. Then open the Network tab, type admin-ajax in the filter box, press Save in the builder, and read the Status column of the rows that appear.
| What you see | Cause | Fix |
|---|---|---|
A notice that Avada Core or Avada Builder needs updating, or the Status page shows plugin versions that do not match the theme; editor half-loads or throws errors from fusion-builder files | The theme was updated but its two plugins were not (or the other way round). Avada only works when all three are on matching versions | Open Avada > Plugins / Add-ons (or follow the update notice) and update Avada Core and Avada Builder to the versions the theme asks for. Updates need the theme registered with its purchase code under Avada > Dashboard; then apply any patches under Avada > Patcher. More in updates stuck |
Red marks on the Status page for memory, max_execution_time or max_input_vars; admin-ajax.php status 500; long pages fail to save or lose sections at the bottom | The server stops the editor: too little memory, too little time, or too few input fields allowed for a long page | Add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php above "That's all, stop editing", and ask the host (or use its "PHP options" screen) to raise max_execution_time and max_input_vars to at least the values the Status page asks for (3000 or more is common). More in "Allowed memory size exhausted" and "Maximum execution time exceeded" |
| Editor loads but looks broken, styles are missing, or it started right after an update or a move to a new host | Avada's generated CSS and JavaScript files are stale or point at the old address | Open Avada > Options > Performance and press Reset Avada Caches, then empty your cache plugin, the host's cache and Cloudflare. After a move, run a search-replace of the old address so the saved settings point at the new one. More in changes not showing on the live site |
| The page opens in the block editor (white canvas, "+" buttons) and there is no Avada Builder button | The block editor took over, or Avada Builder is switched off for this post type | In Avada > Options (Builder section in recent versions) make sure Avada Builder is enabled for Pages, Posts and any portfolio or product type you build with, and that the block editor is not forced on for them. On older setups the free Classic Editor plugin brings the button back |
Pages show raw codes like [fusion_builder_container] or [fusion_text] to visitors | Avada Builder (or Avada Core) is deactivated, or the theme was switched, so nothing turns the codes into a layout | Reactivate both plugins under Plugins (or switch back to Avada). If you are moving away from Avada, each page has to be rebuilt in the new editor first; do not delete the plugins until every page is rebuilt |
| Status 403 when you press Save, or a host or Cloudflare page saying the request was blocked | A firewall rule (ModSecurity, Wordfence, Cloudflare's WAF) read the page's code as an attack | Ask the host to check the firewall log for your IP at that minute and allow that one rule for admin-ajax.php and post.php; in Wordfence use "Allowlist" on the blocked request. Do not switch the whole firewall off. See also 403 Forbidden |
Console errors from files named like rocket-loader, autoptimize or wp-rocket, or only the Live editor hangs | A speed setting delays or combines scripts, including the editor's own; the Live editor also needs the page to load inside a frame | Turn off Cloudflare's Rocket Loader (Speed > Optimization) and exclude logged-in users from JavaScript delay and combine in your speed plugin. If a security plugin sets X-Frame-Options: DENY, change it to SAMEORIGIN |
| None of the above; it started after installing or updating a plugin | A plugin breaks the editor's scripts | Deactivate plugins other than Avada Core and Avada Builder in halves until the editor opens; the last half you switched off holds the culprit. More in a plugin broke the site |
Open two or three pages in both the back-end builder and the Live editor, including the longest one, change a word, save, and reload the public page to see it. Look at Avada > Status again: no red marks. And the Console once more: no red lines from fusion files.
[fusion_...] codes inside each page, and without the plugins every page shows them as raw text.max_input_vars first, then restore the page from its revisions.Most of these take ten minutes once you know which one it is. If you would rather someone else finds and fixes it, that is what the box below is for. Related: WPBakery Page Builder won't load, Divi Builder won't load and Elementor stuck on the loading screen.