Upgrading

WARNING

Always do a database backup before upgrading. You can use the mysqldump, mariadb-dump or pg_dump tools
to quickly export your database as a file.

• With a MariaDB server:

  mariadb-dump -u[user] -p[user_password] [database_name] > dumpfilename.sql

• With a MySQL server:

  mysqldump -u[user] -p[user_password] [database_name] > dumpfilename.sql

Use Composer to update dependencies or Roadiz itself with Standard or Headless editions. Make sure that your Roadiz version constraint is set in your project's composer.json file, then:

composer update -o;

Run database registered migrations (some will be skipped according to your database type). Doctrine migrations are the default method to upgrade all non-node-type-related entities:

bin/console doctrine:migrations:migrate;

To avoid losing sensitive node-sources data, regenerate your node-source entities class files:

bin/console generate:nsentities;

Then, check if there are pending SQL changes due to your Roadiz node-types. This should be addressed with doctrine:migrations:migrate, but you can check with:

bin/console doctrine:schema:update --dump-sql;

If you have any pending SQL changes, you can generate a new migration file in your project with:

bin/console doctrine:migrations:diff;

Adapt the generated migration file if needed, then run:

bin/console doctrine:migrations:migrate;

Finally, clear your app caches:

# Clear cache for each environment
bin/console cache:clear -e dev
bin/console cache:clear -e prod
bin/console cache:pool:clear cache.global_clearer
bin/console messenger:stop-workers

TIP

If you are using a runtime cache like OPcache or APCu, you’ll need to purge it manually
because it can't be done from a CLI interface. As a last resort, restart your php-fpm service.

Versions upgrades

For detailled version upgrades and changes, please refer to the following documents in the Roadiz Core Bundle Dev App repository:

• Project changelog
• Upgrade notes