OXID eShop 7.0.0
Release date: 30-05-2023
The most important changes at a glance
OXID eShop 7.0 natively supports the template engine Twig.
The previously used template engine Smarty is available as an alternative package.
However, we recommend switching to the new standard Twig as soon as possible.
MySQL 8, Composer 2.4 and the image format WebP are supported.
Module handling has been optimized and adapted.
Support for MySQL version 8.0
Support for Composer version 2.4
Switching the default template engine from Smarty to Twig
For more information, see Twig Template Engine.
Optionally, you can still use Smarty.
For more information, see Switching to the legacy Smarty template engine.
Automatic HTML escaping in the frontend.
For more information, see the developer documentation under Check HTML escaping.
Support for WebP image format.
For more information, see Image generation and quality.
Updating Symfony components to version 6.
Improvement of the module system
According to the philosophy of Composer, module files are read exclusively from the
When installing modules, the files are no longer copied to the
For more information, see our developer documentation at Module skeleton: metadata, composer and structure.
We have adjusted the structure of the configuration files.
For more information, see
When updating to version 7, it is therefore necessary that you transfer your custom modules to the new structure.
For more information, see Check changes in the module handler.
The commands for handling modules have changed.
For more information, see
Tracking URL per shipping method
Store one tracking URL per shipping method.
As soon as the parcel ID (depending on the shipping provider tracking code, parcel label number, parcel reference, shipment number, etc.) has been entered with the order, the tracking link consisting of the tracking URL and the parcel ID of the order will be available.
For more information, see Tracking-URL.
Setup via command line
To simplify the implementation of your project, as an alternative to the web-based setup, you can create and configure your OXID eShop via the command line.
You have the following options on the OXID eShop console:
oe:setup:shopto create the database and configure your OXID eShop.
You pass the necessary information for this with parameters.
Install demo data with
Create the store administrator with
If you have OXID eShop Professional or Enterprise edition, add license keys with
It is technically not possible to replace existing license keys with new ones. Therefore, if you replace an existing license key with another one, delete all license keys first with
oe:license:clearand then add the license keys again.
For more information, see Setup via command line.
We have removed the following deprecated functions.
Use the native PHPUnit and Codeception functionality instead of the test library.
For more information, see the developer documentation under Testing.
The RSS functionality has been dropped.
Login via LDAP
If you have an LDAP environment, you need to implement your own login solution.
Credit card as payment method
We no longer support the credit card payment method implemented in OXID eShop for security reasons.
Use the module of a payment provider to offer credit card payment to your customers.
With the introduction of the Flow theme (OXID eShop 6.0.0), you could already access news underonly via a link in the footer.
To present news or offers, we recommend to implement landing pages with Visual CMS (for Professional and Enterprise Edition) in the future.
Encrypted values in the database
We have removed the native encryption of the store configuration in the
oxconfig table, because MySQL 8.0 does not support this feature anymore.
Components of the compilation
The compilation contains the following components:
Visual CMS 4.0.1 (PE/EE)
For the system requirements, see Server and system requirements.
To install, follow the instructions under Installation.
Many thanks to your merge requests published with this release!