After a database copy
Rewriting the production domain
A database copied from production keeps carrying its original domain across dozens of columns: CMS content, blocks, e-mail templates, configuration, links typed by hand into product descriptions. A blind search-and-replace over the dump breaks serialised values and silently corrupts entire configurations.
- Scan
Enter the production domain exactly as it appears in the database, without the protocol if that is how it is stored. The module walks the shop's text columns and hands you the list of table/column pairs concerned, with occurrence counts.
- Dry run
The dry run works out what would change without writing anything. It stays available with the shop open: you can survey the ground before deciding anything.
- Rewrite
Rewriting runs column by column, each one confirmed. Serialised values are handled separately: the declared length of every string is recomputed, so the value stays readable by PHP after replacement.
A real write requires a shop closed to the public. Running this against production would replace its domain with the staging one — an incident you only recover from by restoring a backup. The module therefore refuses to write while maintenance mode is off, and offers a direct link to turn it on.