This documentation is for a version that has reached its End Of Life. Such versions are no longer supported and don't receive security updates. Consider updating to a newer version.
This introduces changes from the relevant website skeleton and results in conflicts.
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 ezsystems package, remove it. You can check how the package is used with composer why <packageName>.
Keep the dependencies listed in the website skeleton.
Tip
You can also approach resolving conflicts differently:
run git checkout --theirs composer.json to get a clean composer.json from the skeleton
and then manually add any necessary changes from your project.
Caution
It is impossible to update an Enterprise edition (ezsystems/ezplatform-ee)
to an Ibexa Content edition.
Also, make sure that composer.json has the following repositories entry:
In production, replace the old repository with the new one.
But as a developer, you may need to go back to an earlier version, and should keep the old repository as well.
For example, your auth.json may look like this:
If you are updating from an installation based on the ezsystems/ezplatform-ee metarepository,
run the following command to upgrade your database:
1
phpbin/consoleibexa:upgrade
Caution
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 config/ezplatform.yaml:
1
- 60 # Components
If you are upgrading between Ibexa Commerce versions,
add the content/read Policy with the Owner Limitation set to self to the "Ecommerce registered users" Role.