Skip to content

Commit 2ea26c5

Browse files
committed
Move "4.6.x to v4.6.latest" to a new page
1 parent 39d1ae4 commit 2ea26c5

File tree

3 files changed

+123
-112
lines changed

3 files changed

+123
-112
lines changed

docs/update_and_migration/from_4.5/update_from_4.5.md

Lines changed: 2 additions & 111 deletions
Original file line numberDiff line numberDiff line change
@@ -473,115 +473,6 @@ php bin/console ibexa:elasticsearch:put-index-template --overwrite
473473
php bin/console ibexa:reindex
474474
```
475475

476-
<!-- vale Ibexa.VariablesVersion = NO -->
476+
## Update to v4.6.latest
477477

478-
## v4.6.2
479-
480-
#### Database update
481-
482-
Run the following scripts:
483-
484-
=== "MySQL"
485-
486-
``` bash
487-
mysql -u <username> -p <password> <database_name> < vendor/ibexa/installer/upgrade/db/mysql/ibexa-4.6.1-to-4.6.2.sql
488-
```
489-
490-
=== "PostgreSQL"
491-
492-
``` bash
493-
psql <database_name> < vendor/ibexa/installer/upgrade/db/postgresql/ibexa-4.6.1-to-4.6.2.sql
494-
```
495-
496-
## v4.6.3
497-
498-
### Notification config update
499-
500-
The configuration of the package `ibexa/notifications` has changed.
501-
This package is required by other packages, such as `ibexa/connector-actito` for [Transactional emails](https://doc.ibexa.co/en/latest/commerce/transactional_emails/transactional_emails/), `ibexa/payment`, or `ibexa/user`.
502-
503-
If you are customizing the configuration of the `ibexa/notifications` package, and using SiteAccess aware configuration to change the `Notification` subscriptions, you have to manually change your configuration by using the new node name `notifier` instead of the old `notifications`.
504-
505-
For example, the following v4.6.2 config:
506-
507-
```yaml hl_lines="4"
508-
ibexa:
509-
system:
510-
my_siteacces_name:
511-
notifications: # old
512-
subscriptions:
513-
Ibexa\Contracts\Shipping\Notification\ShipmentStatusChange:
514-
channels:
515-
- sms
516-
```
517-
518-
becomes the following from v4.6.3:
519-
520-
```yaml hl_lines="4"
521-
ibexa:
522-
system:
523-
my_siteacces_name:
524-
notifier: # new
525-
subscriptions:
526-
Ibexa\Contracts\Shipping\Notification\ShipmentStatusChange:
527-
channels:
528-
- sms
529-
```
530-
531-
## v4.6.4
532-
533-
#### Database update
534-
535-
Run the following scripts:
536-
537-
=== "MySQL"
538-
539-
``` bash
540-
mysql -u <username> -p <password> <database_name> < vendor/ibexa/installer/upgrade/db/mysql/ibexa-4.6.3-to-4.6.4.sql
541-
```
542-
543-
=== "PostgreSQL"
544-
545-
``` bash
546-
psql <database_name> < vendor/ibexa/installer/upgrade/db/postgresql/ibexa-4.6.3-to-4.6.4.sql
547-
```
548-
549-
## v4.6.8
550-
551-
To avoid deprecations when updating from an older PHP version to PHP 8.2 or 8.3, run the following commands:
552-
553-
``` bash
554-
composer config extra.runtime.error_handler "\\Ibexa\\Contracts\\Core\\MVC\\Symfony\\ErrorHandler\\Php82HideDeprecationsErrorHandler"
555-
composer dump-autoload
556-
```
557-
558-
## v4.6.9
559-
560-
No additional steps needed.
561-
562-
## v4.6.10
563-
564-
A command to deal with duplicated database entries, as reported in [IBX-8562](https://issues.ibexa.co/browse/IBX-8562), will be available soon.
565-
566-
## v4.6.11
567-
568-
### Ibexa Cloud
569-
570-
Update Platform.sh configuration for PHP and Varnish.
571-
572-
Generate new configuration with the following command:
573-
574-
```bash
575-
composer ibexa:setup --platformsh
576-
```
577-
578-
Review the changes applied to `.platform.app.yaml` and `.platform/`,
579-
merge with your custom settings if needed, and commit them to Git.
580-
581-
## v4.6.12
582-
583-
If the new bundle `ibexa/core-search` has not been added by the recipies, enable it by adding the following line in `config/bundles.php`:
584-
585-
```php
586-
Ibexa\Bundle\CoreSearch\IbexaCoreSearchBundle::class => ['all' => true],
587-
```
478+
Now, proceed to the last step, [updating to the latest v4.6 patch version](update_from_4.6.md).
Lines changed: 118 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,118 @@
1+
---
2+
description: Update your installation to the latest v4.6 version from an earlier v4.6 version.
3+
---
4+
5+
# Update from v4.6.x to v4.6.latest
6+
7+
<!-- vale Ibexa.VariablesVersion = NO -->
8+
9+
## v4.6.2
10+
11+
#### Database update
12+
13+
Run the following scripts:
14+
15+
=== "MySQL"
16+
17+
``` bash
18+
mysql -u <username> -p <password> <database_name> < vendor/ibexa/installer/upgrade/db/mysql/ibexa-4.6.1-to-4.6.2.sql
19+
```
20+
21+
=== "PostgreSQL"
22+
23+
``` bash
24+
psql <database_name> < vendor/ibexa/installer/upgrade/db/postgresql/ibexa-4.6.1-to-4.6.2.sql
25+
```
26+
27+
## v4.6.3
28+
29+
### Notification config update
30+
31+
The configuration of the package `ibexa/notifications` has changed.
32+
This package is required by other packages, such as `ibexa/connector-actito` for [Transactional emails](https://doc.ibexa.co/en/latest/commerce/transactional_emails/transactional_emails/), `ibexa/payment`, or `ibexa/user`.
33+
34+
If you are customizing the configuration of the `ibexa/notifications` package, and using SiteAccess aware configuration to change the `Notification` subscriptions, you have to manually change your configuration by using the new node name `notifier` instead of the old `notifications`.
35+
36+
For example, the following v4.6.2 config:
37+
38+
```yaml hl_lines="4"
39+
ibexa:
40+
system:
41+
my_siteacces_name:
42+
notifications: # old
43+
subscriptions:
44+
Ibexa\Contracts\Shipping\Notification\ShipmentStatusChange:
45+
channels:
46+
- sms
47+
```
48+
49+
becomes the following from v4.6.3:
50+
51+
```yaml hl_lines="4"
52+
ibexa:
53+
system:
54+
my_siteacces_name:
55+
notifier: # new
56+
subscriptions:
57+
Ibexa\Contracts\Shipping\Notification\ShipmentStatusChange:
58+
channels:
59+
- sms
60+
```
61+
62+
## v4.6.4
63+
64+
#### Database update
65+
66+
Run the following scripts:
67+
68+
=== "MySQL"
69+
70+
``` bash
71+
mysql -u <username> -p <password> <database_name> < vendor/ibexa/installer/upgrade/db/mysql/ibexa-4.6.3-to-4.6.4.sql
72+
```
73+
74+
=== "PostgreSQL"
75+
76+
``` bash
77+
psql <database_name> < vendor/ibexa/installer/upgrade/db/postgresql/ibexa-4.6.3-to-4.6.4.sql
78+
```
79+
80+
## v4.6.8
81+
82+
To avoid deprecations when updating from an older PHP version to PHP 8.2 or 8.3, run the following commands:
83+
84+
``` bash
85+
composer config extra.runtime.error_handler "\\Ibexa\\Contracts\\Core\\MVC\\Symfony\\ErrorHandler\\Php82HideDeprecationsErrorHandler"
86+
composer dump-autoload
87+
```
88+
89+
## v4.6.9
90+
91+
No additional steps needed.
92+
93+
## v4.6.10
94+
95+
A command to deal with duplicated database entries, as reported in [IBX-8562](https://issues.ibexa.co/browse/IBX-8562), will be available soon.
96+
97+
## v4.6.11
98+
99+
### Ibexa Cloud
100+
101+
Update Platform.sh configuration for PHP and Varnish.
102+
103+
Generate new configuration with the following command:
104+
105+
```bash
106+
composer ibexa:setup --platformsh
107+
```
108+
109+
Review the changes applied to `.platform.app.yaml` and `.platform/`,
110+
merge with your custom settings if needed, and commit them to Git.
111+
112+
## v4.6.12
113+
114+
If the new bundle `ibexa/core-search` has not been added by the recipies, enable it by adding the following line in `config/bundles.php`:
115+
116+
```php
117+
Ibexa\Bundle\CoreSearch\IbexaCoreSearchBundle::class => ['all' => true],
118+
```

mkdocs.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -822,7 +822,9 @@ nav:
822822
- Update from v4.4:
823823
- Update to v4.5: update_and_migration/from_4.4/update_from_4.4.md
824824
- Update from v4.5:
825-
- Update to v4.6: update_and_migration/from_4.5/update_from_4.5.md
825+
- Update to v4.6: update_and_migration/from_4.5/update_from_4.5.md
826+
- Update from v4.6:
827+
- Update to v4.6: update_and_migration/from_4.6/update_from_4.6.md
826828
- Migrate to Ibexa DXP:
827829
- Migrate from eZ Publish Platform: update_and_migration/migrate_to_ibexa_dxp/migrating_from_ez_publish_platform.md
828830
- Migrate from eZ Publish: update_and_migration/migrate_to_ibexa_dxp/migrating_from_ez_publish.md

0 commit comments

Comments
 (0)