Update from v4.2.x to v4.3¶
This update procedure applies if you are using a v4.2 installation.
Update from v4.2.x to v4.2.latest¶
Before you update to v4.3, you need to go through the following steps to update to the latest maintenance release of v4.2 (v4.2.3).
Update the application¶
Update from v4.2.latest to v4.3¶
When you have the latest version of v4.2, you can update to v4.3.
Update the application¶
recipes:install command installs new YAML configuration files.
Review the old YAML files and move your custom configuration to the relevant new files.
Run data migration¶
Customer Portal self-registration¶
If you are using Ibexa Experience or Ibexa Commerce, run data migration required by the Customer Portal self-registration feature:
customer Content Type¶
Next, run data migration required by a new User Content Type:
This Content Type is dedicated to registered frontend customers.
This migration is required for all product versions.
Use this option to define a user group that should be migrated to a new Content Type.
--input-user-group- represents the remote ID of a User Group you want to migrate to a new Content Type. After migration, this will also be the ID of a new Private Customer User Group.
--create-content-type- if you add this parameter, the system creates the new Content Type based on the one defined in
Use the parameters below if you need to change a Content Type name during migration, for example because you already have a
customer Content Type,
or you want to define different source Content Type.
If you don't have custom User Content Types, use the basic migration.
--input-user-content-type- defines input Content Type
--output-user-content-type- defines output Content Type
--user- defines the user that this command should be executed as, default is Admin
--batch-limit- defines data limit for migration of one batch, default value is 25
This improvement will prevent logged in backend users from making purchases in the frontend store.
php bin/console ibexa:migrations:migrate -v --dry-run to ensure that all migrations are ready to be performed.
If the dry run is successful, run the following command to execute the above migrations:
Update the database¶
Next, update the database.
Always back up your data before running any database update scripts.
After updating the database, clear the cache.
Do not use
--force argument for
psql commands when performing update queries.
If there is any problem during the update, it is best if the query fails immediately, so you can fix the underlying problem before you execute the update again.
If you leave this for later you risk ending up with an incompatible database, though the problems might not surface immediately.
Apply the following database update scripts:
Ibexa Open Source¶
If you have no access to Ibexa DXP's
ibexa/installer package, database upgrade is not necessary.
Ensure password safety¶
Finish the update process: