Updating modules and applying changes safely

Module updates in production, noupdate data, version bumps, maintenance windows, and change management for config.

In this lesson

What a module update does
Deploying code changes safely
Controlling configuration changes

Key points

-u reloads code, XML, views; runs migrations; updates schema
noupdate records aren't overwritten on update
Dev → staging → production in a window, with a backup first; never -u all casually
Change log and staging for risky configuration changes

Real-world example

A developer shipped a corrected email template in XML, but customers still got the old text: the template was in a noupdate block. A small post-migration that wrote the new body (after confirming nobody had customised it) applied the fix, and the team documented the rule.

Questions and answers

How do you update two modules from the CLI?

-u mod_a,mod_b with --stop-after-init, then restart the service.

Name a configuration change that needs staging first.

Multi-step routes, costing method, taxes, access rights restructuring.

Read the full lesson, worked example and quiz