A CMS update without downtime: an order, not a button

Updates get postponed because a button once took the site down on a Friday. Then they are feared so long that the postponement itself becomes the hole: an old form plugin, an old core, a fix that shipped half a year ago. You need an order that makes an update dull.

A dull order

• A copy you already know how to restore is taken before the update, not after the error.
• A copy of the site or a stand first, then production. On the stand, walk the homepage, the form and payment.
• Plugins and modules are read against the changelog. A major version is not mixed with a dozen others in one evening.
• A person is named to watch the site in that window, and a way to roll back if the form goes silent.
• After the update, check not only "it opened" but a lead in the inbox or in the CRM.

If there is no stand at all, at least do not update the core and every module with one button during the advertising rush hour. Spread it into a quiet window and start with what fixes a known vulnerability, not with what promises a new block editor.

In Lexora maintenance, updates follow this order, not a mood. If the site has fallen far behind, we first look at what will break, and only then press the button.