Update from 7.x to 7.4
This document describes the update procedure from any previous minor version of the OXID eShop 7 series, 7.x, to the minor release 7.4. This update can involve additional steps due to the possibility of choosing one out of two versions of the preinstalled Content & Media Bundle.
Preparation
Verify you are at least on any 7.x version older than 7.4.
Verify what OXID eShop edition you are running (Enterprise, Professional or Community).
Do a backup of your database.
Do a backup of your filesystem.
Decide what Content & Media Bundle you want to use after the update.
OXID eShop 7.4 has the new Content & Media Bundle 9 preinstalled. This includes the following extensions:
Media Library 4
WYSIWYG Editor 6
Visual CMS 9 (Enterprise and Professional Edition only)
Using the new bundle, requires migration of existing content. If you do not want to use the updated extensions, you can preconfigure your update to stay on the last major edition of the Content & Media Bundle. This includes the following extensions:
Media Library 3.0.0
WYSIWYG Editor 5.0.1
Visual CMS 8.0.2 (Enterprise and Professional Edition only)
To decide which bundle version to use, please refer to our Release Notes.
Procedure
Depending on your edition and decision about the Content & Media Bundle, the update procedure consists of up to five steps:
Step 1: Preconfigure the Content & Media Bundle
If you decide for the new Content & Media Bundle 9, you can skip this step and continue with Step 2: Set the Target Version.
If you decide to keep the Content & Media Bundle 8 and you have an OXID eShop Enterprise or Professional Edition, run the following three commands:
composer require oxid-esales/media-library-module:^3.0 --no-update
composer require ddoe/wysiwyg-editor-module:^5.0 --no-update
composer require ddoe/visualcms-module:^8.0 --no-update
If you decide to keep the Content & Media Bundle 8 and you have an OXID eShop Community Edition, run the following two commands:
composer require oxid-esales/media-library-module:^3.0 --no-update
composer require ddoe/wysiwyg-editor-module:^5.0 --no-update
Step 2: Set the Target Version
If you have OXID eShop Enterprise Edition, run the following command:
composer require oxid-esales/oxideshop-metapackage-ee:v7.4.0 --no-update
If you have OXID eShop Professional Edition, run the following command:
composer require oxid-esales/oxideshop-metapackage-pe:v7.4.0 --no-update
If you have OXID eShop Community Edition, run the following command:
composer require oxid-esales/oxideshop-metapackage-ce:v7.4.0 --no-update
Step 3: Run the Update Process
In any case, run the following commands to update your OXID eShop:
composer update --no-plugins --no-scripts --no-dev --with-all-dependencies
composer update --no-dev
./vendor/bin/oe-console oe:cache:clear
./vendor/bin/oe-eshop-db_migrate migrations:migrate
./vendor/bin/oe-eshop-db_views_generate
Step 4: Adjust the Rewrite Conditions
A rewrite condition in previous OXID eShop versions restricts the use of specific brand names. The OXID eShop’s update behavior does not replace your .htaccess file with a new one, since this file is typically customized. Therefore, you must modify the file manually.
Open the file source/.htaccess.
Search for the affected rewrite condition:
RewriteCond %{REQUEST_URI} !(\/admin\/|\/Core\/|\/Application\/|\/export\/|\/modules\/|\/out\/|\/Setup\/|\/tmp\/|\/views\/)
Replace the first instance with the following condition:
RewriteCond %{REQUEST_URI} !^(\/admin\/|\/Core\/|\/Application\/|\/export\/|\/modules\/|\/out\/|\/Setup\/|\/tmp\/|\/views\/)
Repeat this for the second affected instance.
Save the file.
Step 5: Migrate Content and Media
If you decided to keep the Content & Media Bundle 8, you can skip this step. Your Update is finished.
If you decided for the new Content & Media Bundle 9 and you are running an OXID eShop Enterprise or Professional Edition, please see the section Update in our Content & Media Bundle documentation to finish your update.
If you decided for the new Content & Media Bundle 9 and you are running an OXID eShop Community Edition, please see the section Introduction of Media IDs in our Content & Media Bundle documentation to finish your update.