Installing a patch update

Perform a patch update of your OXID eShop if required.

For example, use the following steps to update the compilation from an existing version 6.4.x to version 6.4.2.


Data loss

To avoid possible data loss, do the following:

  • Always run the update in a test environment, a copy of your current store, first.

  • Always proceed as follows when updating:

    1. Create a backup of the store files and database before the update.

    2. After the update, test the store again.
      In particular, check whether the ordering process and the payment and shipping methods work.


  1. Upgrade Composer to version 2.2.23


    Composer 2.3.x is not supported.

    If you have Composer 2.3.x, install Composer 2.2.23 as follows:

    composer selfupdate 2.2.23
  2. Change to the main store directory (in our example /var/www/oxideshop/).

    cd /var/www/oxideshop/
  3. In the composer.json file located in the main store directory, update the metapackage version.
    To do this, do the following:

    1. In the following sample command, adjust the version number of the metapackage according to the new store edition:

      composer require --no-update oxid-esales/oxideshop-metapackage-<edition type: ce, pe, or ee>:v<version number>.
    2. Run the command, in our example for updating a community edition 6.4.1 to 6.4.2:

      composer require --no-update oxid-esales/oxideshop-metapackage-ce:v6.4.2
  4. Update the required libraries.
    To do this, run the following composer command.
    Optional: If you don’t need the development-related files, use the --no-dev parameter.

    composer update --no-plugins --no-scripts --no-dev
  5. Download the new compilation.
    To do this, run the following composer command.

    composer update --no-dev
  6. For store files, themes and modules, confirm that the update overwrites existing files.

  7. To ensure that the cached items do not contain incompatibilities, empty the /tmp directory.

    rm -rf source/tmp/*
  8. Migrate the database.

    vendor/bin/oe-shop-db_migrate migrations:migrate
  9. Regenerate the database views.
    Background: Depending on the changes and store edition, the store may go into maintenance mode after the update.
    To prevent this, regenerate the database views with the following command:



The update is finished. If you open the store as administrator, the new version is displayed in the upper right corner.