When a Divi 5 site breaks after an update, find the cause before you change anything. First read what Divi and the server report, then use Safe Mode to switch the plugins, the child theme or your custom code off for yourself only, until the problem goes away. Divi Doctor by YemLogic does both without changing what visitors see. This page gives the order to check things in, which screen answers which question, and what to do once you know the cause.
Note: The diagnostics and the Safe Mode controls by group are in both plugins, the free Doctor for Divi and Divi Doctor Pro. Safe Mode plugin by plugin, Layout History and Monitoring are part of Divi Doctor Pro. See Doctor for Divi (free) and Divi Doctor Pro.
Before you change anything
- Write down what was updated (Divi, a plugin, WordPress or PHP) and when the problem started. The newest update is the first suspect, not the only one.
- Make a backup, or work on a staging copy if your host offers one.
- Clear your page cache and Divi’s static CSS files, then check the page again in a private browser window. If the problem is gone, it was a stale cache.
Every step below only reads your site, or changes what you alone see, until you decide to fix something.
Step 1: Read the Overview
Go to Divi Doctor → Overview. Under Most likely issues, ranked, it lists up to eight checks that came back as Issue or Check, the ones most likely to cause a visible problem first. Treat each row as a lead to follow, not a final verdict. The Environment section at the bottom shows your Divi, WordPress and PHP versions, so you can confirm what the update changed.
Step 2: Check what Divi and the server report
Go to Divi Doctor → Diagnostics. Each row shows a verdict, the value Divi Doctor measured and the reason. Three checks matter most after an update:
- Static-CSS pipeline on the Site Checks tab. Divi 5 serves its page CSS as files from its cache folder. If Divi can’t write there, pages load with missing styles. et-cache writable: Issue means the folder needs fixing, which your host can do.
- Reversion watch on the same tab. A Theme Builder layout marked changed without an edit was rewritten directly in the database, for example by a backup that restored itself, a staging sync or a migration.
- Exception Watch. It lists PHP errors from the Divi theme, your child theme, Divi’s cache folder and the Divi Builder plugin, with the file and line. A FATAL row means that request stopped there. The file path tells you whether the error comes from Divi or from your child theme.
What each check reports is in Site checks, Exception Watch and hosting.
Step 3: A page lost its styling? Run Page Scan
One missing brace in a Custom CSS field can break the styling of a whole page. Go to Divi Doctor → Diagnostics → Page Scan and choose the page. Page Scan checks the Custom CSS fields of that page and its modules, every Theme Builder layout and off-canvas panel, and the Additional CSS, and names the field and the line to fix. See Page Scan.
Step 4: Narrow it down with Safe Mode
Divi’s own Safe Mode switches off every plugin, the child theme and all custom code at once. That tells you that something on the site causes the problem, but not what. With the Safe Mode controls you choose what it switches off. Only you see Safe Mode, in your browser; visitors and other users keep getting the normal site, and the site’s list of active plugins is never changed.
- Go to Divi Doctor → Safe Mode and click Enable on the Safe Mode controls card.
- Leave everything ticked and click Turn Safe Mode on. Open the page with the problem in the same browser. If the problem is still there, it doesn’t come from a plugin, the child theme or custom code.
- If the problem is gone, untick the Custom CSS and the Integration code and click Save choices. Problem back? It’s in that code.
- Still gone? Untick the child theme and save. Problem back? It’s in the child theme.
- Still gone? A plugin causes it. In Divi Doctor Pro, keep half of the plugins active, check the page, and keep halving until one plugin is left. In the free plugin, deactivate plugins one at a time on a staging copy of the site.
- Click Turn Safe Mode off when you’re done.
While the controls are enabled, Divi Doctor itself stays active in Safe Mode. To rule it out, disable the controls and use Divi’s Safe Mode from Divi → Support Center. Every choice and safety net is in Safe Mode controls.
Step 5: A header or footer changed? Restore it
If a Theme Builder header, body or footer looks different after an update, a sync or someone’s edit, restore its earlier version. WordPress keeps a revision every time a Theme Builder layout is saved, and Layout History in Divi Doctor Pro lists those revisions, shows what changed and restores the one you pick. Switch on Layout history (revisions) under Divi Doctor → Features, then go to Divi Doctor → Layout History → Theme Builder. See Theme Builder and Divi Library history.
Step 6: The problem comes and goes? Turn on Monitoring
Some problems only show up after a few quiet days, such as pages that suddenly lose their styling. Monitoring in Divi Doctor Pro takes a snapshot every couple of hours: whether the home page loads Divi’s CSS, Divi’s shared stylesheet, the cache folder, the object cache and whether a layout changed. When the problem comes back, find the first BROKEN row and look at what changed in it and in the rows just before. See Monitoring.
When you know the cause
| The cause | What to do |
|---|---|
| A plugin | Check for a newer version first. If the update itself caused it, go back to the previous version on a staging copy: for plugins from WordPress.org, a rollback plugin such as WP Rollback can install an earlier version. Tell the plugin’s developer what you found. |
| The child theme | Fix the file and line that Exception Watch shows, or ask whoever wrote the child theme. |
| Custom CSS or Integration code | Fix the field and line that Page Scan names, or remove the code you added most recently. |
| Divi itself | Send the Exception Watch row, with its file and line, to Divi’s support. |
| The server | Send the Site Checks row, for example et-cache writable: Issue, to your host. |
| A Theme Builder layout | Restore its earlier version with Layout History, then clear your page cache. |
Which screen answers which question
| Question | Where | Plugin |
|---|---|---|
| What looks most likely? | Overview | Both |
| Is Divi’s CSS cache folder working? | Diagnostics → Site Checks → Static-CSS pipeline | Both |
| Did a layout change without anyone editing it? | Diagnostics → Site Checks → Reversion watch | Both |
| Does Divi or the child theme throw PHP errors? | Diagnostics → Exception Watch | Both |
| Which CSS field broke this page? | Diagnostics → Page Scan | Both |
| Is it a plugin, the child theme or custom code? | Safe Mode, by group | Both |
| Which plugin is it? | Safe Mode, plugin by plugin | Pro |
| Can I get yesterday’s header back? | Layout History | Pro |
| What changed just before it broke? | Monitoring | Pro |
Questions
How do I find which plugin broke my Divi site?
Turn on Safe Mode with the Safe Mode controls in Divi Doctor. If the problem goes away with plugins switched off and comes back when you keep them, a plugin causes it. In Divi Doctor Pro you then keep half of the plugins active, check the page and keep halving until one plugin is left. In the free Doctor for Divi, deactivate plugins one at a time on a staging copy.
Will my visitors see Safe Mode while I test?
No. Divi’s Safe Mode only applies to the logged-in user who turned it on, in that browser, for up to one day. Visitors and other users keep getting the normal site, with or without the Safe Mode controls.
Can I find the cause without deactivating plugins on my live site?
Yes. Safe Mode switches plugins off for your browser only, and the site’s list of active plugins is never changed. Only the last step of the free plugin’s method, deactivating plugins one at a time, belongs on a staging copy.
My Divi pages lost their styling after an update. What should I check first?
Clear your page cache and Divi’s static CSS files, then open the page in a private window. If it is still unstyled, check Static-CSS pipeline under Divi Doctor → Diagnostics → Site Checks: Divi 5 serves page CSS as files from its cache folder, and pages load without styles when Divi can’t write there. If one page is affected, run Page Scan on it.
How is this different from the Health Check & Troubleshooting plugin?
Health Check’s Troubleshooting mode works with any theme: it switches off all plugins and uses a default theme, for your user only. Divi Doctor’s Safe Mode controls use Divi’s own Safe Mode, so Divi keeps running while you choose to switch off the plugins, the child theme, the Custom CSS or the Integration code. Divi Doctor also checks things only a Divi site has, such as Divi’s CSS cache folder, Theme Builder layouts and PHP errors from Divi.
Does Divi Doctor change my site while it checks?
No. The diagnostics are read-only: they measure and report. Safe Mode only changes what you see in your own browser. A change happens only when you make it, for example when you restore a layout in Layout History.
See also Safe Mode controls, Site checks, Exception Watch and hosting and FAQ and troubleshooting.