Standard update

This document describes patches and minor updates of OXID eShop. Follow the steps below to update the compilation from an existing version to a newer version.

Note

Updates should always be installed in a test or development environment. Backup the shop files and the database before updating. Disable all modules and check whether the shop works in general. After updating, test the shop again, paying special attention to the ordering process as well as payment and shipping methods.

Note

To execute commands via the command line, open a shell in the shop root directory and run commands in there.

schritt Optional: Update Composer

Please read the Composer documentation for more information.

Hint

The version of the composer must correspond to the supported one in the metapackage.

schritt Specifying the target version of the update

In the composer.json file, the version of the metapackage must be updated.

Example of an update for a Community Edition 7.0.0 to 7.1.0:

composer require --no-update oxid-esales/oxideshop-metapackage-ce:v7.1.0

Hint

The name of the metapackage must be adapted to the used shop edition.

schritt Updating dependencies

Specify the --no-dev parameter if the development-related files are not required.

composer update --no-plugins --no-scripts --no-dev

schritt Obtaining new compilation

The following command executes all scripts to obtain the new compilation. For shop files, themes and modules, you will need to confirm that the update will overwrite the existing files.

composer update --no-dev

schritt Deleting cache files

rm -rf source/tmp/*

schritt Migrating database

./vendor/bin/oe-eshop-db_migrate migrations:migrate

schritt Optional: Generating views

Depending on changes and shop edition you might see the maintenance mode in the shop as long as the views are not generated again.

./vendor/bin/oe-eshop-db_views_generate

Hint

Usually required when updating an Enterprise Edition.

This completes the updating process.