Blog / Tutoriels

Update a WordPress fleet without breaking a checkout

A WordPress update on twenty sites is a lot, a copy, and a way back. Not twenty wp-admin tabs left open on a Tuesday.

A WordPress update is cheap until it is twenty sites and one of them takes payments. Then the job is not “click update”. It is a lot, a copy, a way back, and a log when the client asks what you touched.

Do not start with everything

Start with the list: which cores, which plugins, which PHP. A site on 7.4 does not take the same lot as a shop on 8.2. The inventory is the plan. The button comes after.

Copy, then the lot, then check checkout

wpmcp takes a copy, runs what you confirmed, keeps a rollback. You still open the shop URL. If the payment form 500s, you go back on that site, not on the nineteen that passed.

Tuesday is a lot, not twenty tabs

Twenty wp-admin sessions is how updates get skipped. One recap, one confirm, one log. That is a WordPress update process an agency can defend.