Update from v4.4.x to v4.5¶
This update procedure applies if you are using a v4.4 installation.
Update from v4.4.x to v4.4.latest¶
Before you update to v4.5, you need to go through the following steps to update to the latest maintenance release of v4.4 (v4.4.4).
Update the application to v4.4.latest¶
Temporary need of Composer conflict
To go through this update, map the conflicting packages in your composer.json
file as following:
1 2 3 4 |
|
Run:
1 |
|
1 |
|
1 |
|
Remove temporary Composer conflict
You can now remove the temporary Composer conflict
entries from your composer.json
file:
1 2 3 4 |
|
Update from v4.4.latest to v4.5¶
When you have the latest version of v4.4, you can update to v4.5.
Update the application¶
First, run:
1 2 |
|
1 2 |
|
1 2 |
|
The recipes:install
command installs new YAML configuration files.
Review the old YAML files and move your custom configuration to the relevant new files.
Define measurement base unit in configuration¶
If your installation has defined measurement units in the configuration,
you need to specify one of them as base unit in the config/packages/ibexa_measurement.yaml
file:
1 2 3 4 |
|
Next, add unit conversion to src/bundle/Resources/config/services/conversion.yaml
.
For more information, see Modify and add Measurement types and units.
Update the database¶
Next, update the database:
Caution
Always back up your data before running any database update scripts.
After updating the database, clear the cache.
Do not use --force
argument for mysql
/ 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:
1 |
|
1 |
|
Migrate richtext namespaces¶
If you earlier upgraded from v3.3 to v4.x and haven't run the migrate script yet, do it now, run:
1 |
|
Ibexa Open Source¶
If you have no access to Ibexa DXP's ibexa/installer
package, apply the following database update:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
|
Clean-up taxonomy database¶
If you didn't run it already when migrating from 4.2 to 4.3, run the following command for each of your taxonomies to ensure that there are no Content items orphaned during deletion of subtrees inherited from the earlier version's database:
php bin/console ibexa:taxonomy:remove-orphaned-content <taxonomy> --force
For example:
1 2 |
|
Finish code update¶
Finish the code update by running:
1 |
|
Run data migration¶
If you are using Ibexa Experience or Ibexa Commerce, you can now run data migration required by the Customer Portal and Commerce features to finish the update process:
- Customer Portal
1 2 |
|
- Corporate access role update
1 2 |
|
- Corporate account
This migration allows all company members to shop in the frontend shop. If you have implemented business logic that depends on keeping company members out of the frontend shop, you can skip it:
1 2 |
|
- Storefront user update
1 2 |
|
- Shipment permissions
1 2 |
|
- Order permissions
1 2 |
|
v4.5.2¶
Database update¶
Run the following scripts:
1 |
|
1 |
|
v4.5.3¶
Database update ¶
Run the following scripts:
1 |
|
1 |
|
v4.5.4¶
Database update¶
Run the following scripts:
1 |
|
1 |
|