Updating Ibexa DXP to v3.3¶
Ibexa DXP v3.3 uses Symfony Flex. When updating from v3.2 to v3.3, you need to follow a special update procedure.
If you are updating from an earlier version, start with updating your installation to v3.2.
First, create an update branch in git and commit your work.
If you have not done it before, add the relevant meta-repository as an
It is good practice to make git commits after every step of the update procedure.
Merge the special
v3.2-to-v3.3-upgrade update branch into your project:
This will introduce changes from the website skeleton
and result in conflicts in
Resolve the conflicts in the following way:
- Make sure all automatically added
ezsystems/*packages are removed. If you explicitly added any packages that are not part of the standard installation, retain them.
- Review the rest of the packages. If your project requires a package, keep it.
- If a package is only used as a dependency of an
ezsystemspackage, remove it. You can check how the package is used with
composer why <packageName>.
- Keep the dependencies listed in the website skeleton.
extra.symfony.endpoint is set to
For all dependencies that you removed from
composer.json, check if the
bin folder contains files that will not be used and remove them, for example:
Add your Ibexa DXP edition to
composer.json, for example:
It is impossible to update an Enterprise edition (
to an Ibexa Content edition.
Update the app¶
composer update to update the dependencies:
If Composer informs you that the
composer.lock file is out of date, run
composer update again.
Update recipes for third party packages¶
composer recipes to get a list of all the available recipes.
For every recipe that needs updating, run:
Review changes from each package and integrate them into your project.
Install Ibexa recipes¶
Install recipes for Ibexa packages for your product edition, for example:
Review the changes and add them to your project.
Then, run the post-installation command:
Configure the web server¶
Add the following rewrite rule to your web server configuration:
Update the database¶
Before starting this step, back up your database.
Apply the following database update script:
If you are updating from an installation based on the
run the following command to upgrade your database:
You can only run this command once.
Check the Location ID of the "Components" Content item and set it as a value of the
content_tree_module.contextual_tree_root_location_ids key in
If you are upgrading between Ibexa Commerce versions,
content/read Policy with the Owner Limitation set to
self to the "Ecommerce registered users" Role.
Updating to 3.3.2¶
To update to v3.3.2, if you are using MySQL, additionally run the following update script:
Update entity managers¶
Version v3.3.2 introduces new entity managers. To ensure that they work in multi-repository setups, you must update the GraphQL schema. You do this manually by following this procedure:
Update your project to v3.3.2 and run the
php bin/console cache:clearcommand to generate the service container.
Run the following command to discover the names of the new entity managers. Take note of the names that you discover:
php bin/console debug:container --parameter=doctrine.entity_managers --format=json | grep ibexa_
For every entity manager prefixed with
ibexa_, run the following command:
php bin/console doctrine:schema:update --em=<ENTITY_MANAGER_NAME> --dump-sql
Review the queries and ensure that there are no harmful changes that could affect your data.
For every entity manager prefixed with
ibexa_, run the following command to run queries on the database:
php bin/console doctrine:schema:update --em=<ENTITY_MANAGER_NAME> --force
Enable Commerce features¶
With the v3.3.2 update, Commerce features in Experience and Content editions are disabled by default. If you use these features, after the update refer to Enable Commerce features and manually enable them.
Finish the update¶
Finish the update by running the following commands: