Enfold fix
Enfold Styles Broken After an Update? Clear the Merged Files
The update finished, or the site moved to a new host, and Enfold now looks like a draft of itself: default fonts, wrong colors, a menu stacked down the left side. In most cases nothing was lost. Enfold writes its styling into generated files in the uploads folder, and those files are missing, out of date or still describing the old address.
What you are seeing
- Colors and fonts fall back to defaults across the whole site
- The header menu shows as a plain list of links
- Icons appear as empty squares or stray letters
- The site looks right when you are logged in and wrong for visitors
- The browser console lists 404s for files under dynamic_avia
Why it happens on Enfold
Most common first.
- 1
Merged files left over from the previous version
With file merging on, Enfold combines its stylesheets and scripts into single files in wp-content/uploads/dynamic_avia. After an update, cached pages can still point at a merged file that has been replaced or removed. Visitors get a page asking for styles that belong to a theme version no longer installed.
- 2
The dynamic stylesheet was never rebuilt
Your choices under General Styling and Advanced Styling are compiled into a stylesheet in that same folder, and it is rebuilt when theme options are saved. After a migration that skipped part of the uploads folder, or a restore from a partial backup, the file is absent and Enfold falls back to its defaults.
- 3
Generated files still carry the old address
Generated CSS can contain full URLs for fonts, icons and background images. Move the site to a new domain, or from http to https, and those URLs still name the old one. Browsers block or fail the requests, which is why icons turn into squares.
- 4
The server will not let Enfold write
Enfold can create these files only if the uploads folder is writable. A migration that changes file ownership, or a tightly locked host, leaves dynamic_avia read-only. Nothing gets rebuilt then, however many times you press save.
- 5
Child theme copies aimed at the old markup
Copied templates and old CSS in a child theme keep targeting the structure and class names of the version they came from. When the parent changes its markup, those rules stop matching and the copied templates output a structure the new stylesheet does not style.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Back up, then purge the caches you know about
Save files and database first. Then clear your caching plugin, the host's cache and any CDN. If the site is right after that, cached pages were pointing at files that no longer exist and you are finished.
- 2
Turn merging off to see the real state
Go to Enfold, Performance, set both the CSS and the JavaScript file merging and compression options to disabled and save. Load the site in a private window. If the styling returns, the theme is healthy and the merged files were at fault.
- 3
Save the theme options again
Open Enfold, Theme Options and press Save all changes even though you changed nothing. That prompts Enfold to rebuild its dynamic stylesheet from the stored settings, using the address the site has now.
- 4
Clear the old generated files
The Performance tab includes an option for deleting old generated CSS and JavaScript files. Use it, or empty wp-content/uploads/dynamic_avia over SFTP and save theme options once more. Enfold recreates what it needs.
- 5
Confirm the folder can be written
If dynamic_avia stays empty after saving, the server is refusing the write. Tools, Site Health, Info, Filesystem Permissions shows whether WordPress considers the uploads directory writable. If it does not, ask your host to correct the ownership.
- 6
Check the child theme, then merge again
On staging, activate the parent Enfold theme briefly. The parent keeps its own set of theme options, so judge structure, not colors. If the layout holds there, compare each copied file in the child theme with the parent's current version. Once pages look right, switch merging back on and test logged out.
Keep it from coming back
- Switch file merging off before a theme update and back on after you have checked the site
- After any migration or domain change, save theme options once so the generated files are rebuilt
- Let one tool merge CSS and JavaScript: Enfold or an optimization plugin, never both
- Note which Enfold version each copied template in the child theme came from
The permanent fix
A faster Next.js build, with a CMS made for your business
A stylesheet that has to be generated, merged, cached and purged in the right order is a lot of moving parts for what ought to be a file. If the site loses its styling with every update or move, the fragility is in that chain and it will be there next time. On a Next.js build the CSS is compiled once and shipped with the page, and a custom CMS lets your team change content without touching styling at all.
| 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
Very unlikely. Colors, fonts and layout choices are stored in the database, not in the theme folder, so replacing the theme leaves them alone. What goes missing is the generated stylesheet that turns those settings into CSS. Saving theme options rebuilds it.
Logged-in users usually bypass the page cache, so you see a freshly built page that points at the current files. Visitors get a cached copy that still asks for a merged file removed during the update. Purge the page cache and CDN after the generated files are rebuilt, not before.
It sits inside wp-content/uploads and holds files Enfold generates: the stylesheet built from your theme options and any merged CSS and JavaScript. Emptying it is safe where the folder is writable, because Enfold recreates the files when you save theme options. Take a backup first anyway.
You can. The site works without it and simply makes more separate requests per page, which costs less on modern hosting than it once did. If merging has broken the site more than once, leaving it off and relying on a page cache is a reasonable trade.
Keep reading
- ServiceDesign & Layout FixesOverlapping text and broken spacing tell a customer you do not sweat details. We fix the glitches so the site looks as competent as the business.
- 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.
- ServiceWebsite Migration ServicesMove off WordPress, a page builder, an e-commerce platform or a slow host without losing rankings, forms or tracking — inventoried, redirected, watched.