[UPMERGE] 5.0 -> 5.1 - #3132
Open
github-actions[bot] wants to merge 2 commits into
Open
Conversation
Pimcore 12 / DBAL 4 dropped the doctrine "array" and "object" column types, so several CoreShop columns were switched to type "json" (Configuration::data, Index/IndexColumn/FilterCondition configuration, Rule Action/Condition configuration). The old types serialized their values with PHP serialize(), while "json" reads them with json_decode(), so data written by CoreShop 4 is unreadable after the upgrade (e.g. the configuration service and rule conditions/actions blow up). Adds a CoreBundle migration that converts those legacy PHP-serialized values to JSON. Idempotent (skips valid JSON, no-op on fresh installs) and skips tables of bundles that are not installed.
…nfig [Core] Migrate legacy PHP-serialized json columns to JSON (CoreShop 4 -> 5)
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR has been generated automatically.
Remember! The upmerge should always be merged with using
Merge pull requestbutton.In case of conflicts, please resolve them manually with usign the following commands: