OXID eShop v6.0.0 RC3 is published

 Please note that this release contains a fix for a security issue with a CVSS of 8.1. We will hand out more information about it with security bulletin 2017-002. Please also see the FAQ for 2017-002.

Information about changes

  • This release contains a fix for an issue described with security bulletin 2017-002.
  • The pagination has been changed: for example, previously the URL was like “Geschenke/100/” – now it will be “Geschenke?pgNr=99”. In addition, these pages come with the meta tag “noindex, follow”.
  • The PayOne module was updated to v1.0.3. Changes can be found in changelog.

Compilation changes which were introduced can be found in compilation metapackage: https://github.com/OXID-eSales/oxideshop_metapackage_ce/compare/v6.0.0-rc.2…v6.0.0-rc.3

To see the entire change log, please turn to this page: https://github.com/OXID-eSales/oxideshop_ce/blob/master/CHANGELOG.md

Updating and installing OXID eShop v6.0.0 RC3

The most simple way to install the OXID eShop is to run the Composer command and create a project. Please make sure you have the latest version of composer installed by running composer self-update.

By default, Composer installs the OXID eShop compilation including the development ressources (e. g. OXID Testing Library, IDE helper, Codesniffer). If you are planning to install the OXID eShop Compilation on production environments, make sure to add the nodev flag.

  • For Community Edition run:

  • For Professional Edition run:

  • For Enterprise Edition run:

For updating OXID eShop from RC2 to RC3, please run the following steps:

  1. Please edit the oxid-esales/oxideshop-metapackage version requirement in your root composer.json file by changing version to “^v6.0.0-rc.3”.
  2. In the project, run:

    for updating dependencies.
  3. In the project, run

    for executing all necessary scripts.
  4. In the project, run

    for executing possible database migrations.

Please update on your own risk, we recommend installation from scratch.


0.00 avg. rating (0% score) - 0 votes

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *