[4.x] In AssetReferenceUpdater check actual datatype of bard field content #7555
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.
Fixes #7547
This might be a niche use case, but concerns an important part of managing assets, thus might be important.
In the AssetReferenceUpdater (used on deleting, renaming or moving assets) content is being scanned and wherever an asset is being referenced, the reference should be updated.
The error from Issue #7547 appears now, when a Bard Field is assumed to store structured data but instead a (HTML) String is stored. One might expect that this can't happen, but imagine following:
I therefore suggest to not only check for the blueprint setting. Instead, still check if it's a String, and if so choose the right method.