Hire
Docs Navigation Open

Updating Evolution

Update carefully: back up first, preserve customizations, run the updater, and verify the install is closed again.

Updating Evolution CMS is safe when you treat it as a controlled maintenance task rather than a file overwrite with hope.

Safe Update Flow

  1. create a full backup of files and database
  2. review customized bundled snippets, plugins, or modules
  3. prepare the new version in staging if possible
  4. run the update path through the installer
  5. remove or confirm removal of the install directory after completion
  6. clear cache and test the manager and frontend

Important Legacy Detail

If you modified bundled components under their original names, an update may overwrite them. Duplicate and rename custom versions before relying on them long term.

After the Update

  • check manager login
  • check resource rendering and parser output
  • check extras that depend on specific parser or manager behavior

See also Backups and Security.

Previous

Backups

Back up files and database before updates, migrations, and any risky operational change.
Next

Deployment

Move a site between environments by transferring files, database, paths, and config in a controlled order.