5.0.3 to 5.0.4: DB Update #2997
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ibexa-5.0.2-to-5.0.3.sql files have been edited between 5.0.3 and 5.0.4
https://github.com/ibexa/installer/commit/c84c6ad3c5b9b9367fdae85ec1c7c888a298ecd3
If someone ended on v5.0.3, this DB upgrade SQL file won't be played again so the v5.0.4 part must be executed manually.
ibexa_site_public_accessis a site factory table only existing on Experience and Commerce.The
ibexa_site_public_access.tree_root_location_idisn't used until v5.0.4 https://github.com/ibexa/site-factory/commit/f248888b0ccee6f9bee84556455c3e19fe00d8efI added condition to not override
tree_root_location_idif the last request have already been ran.Preview: https://ez-systems-developer-documentation--2997.com.readthedocs.build/en/2997/update_and_migration/from_5.0/update_from_5.0/#database-update_1
Checklist