Details
-
Bug
-
Resolution: Done
-
Medium
-
None
-
None
-
[3.3] - Sprint 3
Description
The following article must be polished to make it readily understandable to the customers:
https://doc.ibexa.co/en/latest/upgrading/upgrading_to_v3/
- review the document and add missing technical details where needed
- change order of the steps
- add information on how the steps should be performed
- add prerequisites to Symfony at the beginning
Feedback from the dev team so far:
| Article | SME | Comment |
|---|---|---|
| SF5, DIC/containers https://doc.ibexa.co/en/latest/upgrading/4_10_upgrade_other/ |
Maciek K. | |
| Field Typeshttps://doc.ibexa.co/en/latest/upgrading/4_3_upgrade_field_types/ | Adam | Looks good |
| Signal slots https://doc.ibexa.co/en/latest/upgrading/4_4_upgrade_signal_slots/ |
Sławek | |
| Online Editor https://doc.ibexa.co/en/latest/upgrading/4_5_upgrade_online_editor/ |
Darek | "Can't think of anything that could be added to the Extra Buttons section" |
| Workflow https://doc.ibexa.co/en/latest/upgrading/4_6_upgrade_workflow/ |
Sławek | |
| REST | Dawid | I do not see a point in adding code samples re. namespace changes. It is basic PHP object programming. For those who do not know where to find it, samples won't change it. |
| SiteFactory https://doc.ibexa.co/en/latest/upgrading/4_9_upgrade_site_factory/ |
Mikołaj A., Michał G. | |
| HTTP cache | Dawid | The list of deprecations and changes is complete. (fix the link to point to the right section of the compatibility breaks list). |
Also - add a link to configuration:
be careful if you upgrade V2 to V3 for solr conf. There is a param to change in solr from the default one for the content changes to appear in solr on publish. https://doc.ezplatform.com/en/3.1/guide/search/solr/#further-configuration
we should update this to add reference to this conf : https://doc.ezplatform.com/en/latest/upgrading/upgrading_to_v3/