Divi Maintenance: Every Update Checked Before It Reaches You

By checking templates rather than sampling pages. The header, footer and body templates are assigned across groups of pages, so one of them shifting affects everything at once while the individual pages you happen to open look untouched. Every assigned template is opened and compared on the clone after an update, before the live site sees it. The residual risk is a template assigned to something nobody remembered, which is why the assignments are written down rather than rediscovered each time.

It goes on the inventory with its version and its last release date, and it becomes a known risk rather than a surprise. An abandoned module usually keeps working on Divi 4 for a long time; the point it stops is a PHP version change or Divi 5. Knowing which module it is, which pages use it, and whether a stock Divi module or a small custom one could replace it turns that from an emergency into a scheduled decision.

That is extremely common, and worth sorting out before an urgent security release arrives. Until a working account is connected, Divi cannot update at all, which also affects what any other job on the site costs. The first month of maintenance includes confirming the connection and telling you who it belongs to, so the question has an answer before it becomes urgent.

Yes. Divi's Role Editor lets each user role keep full page editing while losing access to the Theme Builder and theme options. We set that up, test it with a real editor account, and leave you a note of which roles can reach what, so the next person added to the site gets the right access by default.

No, and that is deliberate. Silently performing a rewrite-level upgrade because it appeared in the updates list is not maintenance. You are kept on a supported Divi 4, told when Divi 5 is relevant to your modules, and given a separate scoped quote when you decide to move.

That is nearly always Divi's static CSS files disagreeing with what the builder is showing you, usually after a release, a colour change or a move between hosts. It sends people looking at their theme, their cache plugin and their CDN in turn, none of which is the cause. It is seconds to resolve once recognised, and re-checking Divi's own performance switches after every release is what stops it recurring.

They are treated as part of the site rather than as personal scratch files, which means they are included in the pre-update backup and checked afterwards. Library items drift out of step with the pages built from them (somebody edits the page, not the source) so where that has happened you get told which ones no longer match, rather than us quietly resaving one over the other.

Mapping the site: Divi and module versions, which modules are third-party and who maintains them, what the child theme changes, which Theme Builder templates exist and where they are assigned, and the licence position. Every one of those shapes how updates are applied, so they are recorded up front. You keep the write-up whether or not you stay with us.

Open all week, 9 to 5 AET. Plan work, update checks and requests are handled in those hours. If the site goes down outside them, after-hours incident help is available at a separate rate, from $649: the emergency WordPress support page sets out how it works.