Modules that stopped following the version
An abandoned module gives a blank page or an error on the new version. We first find out which one, and what replaces it.
We upgrade on a copy, migrate the modules and the custom work, and go live only after ordering, payment and shipping have run through the rehearsal.
An abandoned module gives a blank page or an error on the new version. We first find out which one, and what replaces it.
Changes written into templates or overrides are lost in the upgrade. We collect them and rebuild them on the new version.
Payment and shipping modules are the most sensitive. We run them through a real process before going live.
We review the installed modules, the theme, the overrides and the PHP version, and write down what will break.
The upgrade is built on a copy of the webshop. The live instance is untouched until the end.
Modules are replaced or substituted, custom development is migrated.
Ordering, payment, shipping, invoicing and e-mails are all run through on the copy.
The switch happens at an agreed time, with a rollback point.
We watch the error log for days after go live and fix what surfaces.
We look at the webshop and write down what can be upgraded, what has to be replaced, and how much work it is.
The upgrade is completed on the copy and the full purchase flow is rehearsed.
We switch at an agreed time, then watch the shop for a few days.
Send the webshop address and what the problem is. We look at it and reply within two working days with what we suggest and what it costs.