Update from v4.1.x to v4.2¶
This update procedure applies if you're using a v4.1 installation.
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 |
|
Update from v4.1.x to v4.1.latest¶
Before you update to v4.2, you need to go through the following steps to update to the latest maintenance release of v4.1 (v4.1.5).
Update the application¶
Run:
1 |
|
1 |
|
1 |
|
VCL configuration for Fastly¶
The Fastly .vcl
configuration files have changed.
Follow the upgrade steps below to update them:
- Locate the
vendor/ibexa/fastly/fastly/ez_main.vcl
file and update your VCL file with the recent changes. - Do the same with
vendor/ibexa/fastly/fastly/ez_user_hash.vcl
. - Upload a new
snippet_re_enable_shielding.vcl
snippet file, based onvendor/ibexa/fastly/fastly/snippet_re_enable_shielding.vcl
.
Once the VCL configuration has been updated, you may enable Fastly Shielding if you prefer.
Update from v4.1.latest to v4.2¶
When you have the latest version of v4.1, you can update to v4.2.
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.
Run data migration¶
Next, run data migration required by Product Categories:
1 |
|
If you're using Ibexa Experience or Ibexa Commerce, run data migration required by the Customer portal feature:
1 |
|
If you're using Ibexa Commerce, additionally run:
1 |
|
Run 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:
1 |
|
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.
Don't use --force
argument for mysql
/ psql
commands when performing update queries.
If there is any problem during the update, it's 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 2 |
|
1 2 |
|
Ibexa Open Source¶
If you have no access to Ibexa DXP's ibexa/installer
package, database upgrade isn't necessary.
Ensure password safety¶
Following Security advisory: IBEXA-SA-2022-009, unless you can verify based on your log files that the vulnerability has not been exploited, you should revoke passwords for all affected users.
Remove node_modules
and yarn.lock
¶
Next, remove node_modules
and yarn.lock
before running composer run post-update-cmd
,
otherwise you can encounter errors during compiling.
1 2 |
|