Handle existing RichTextEditorValue when parsing from markup or JSON structure #19266
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.
Prerequisites
Fixes #19274
Description
We had this issue come in through Umbraco support where the customer was using a
SendingContentNotification
to hide certain properties from certain editors.They found when doing this with a rich text editor, any existing value would get lost on save (replaced with "Umbraco.Cms.Core.RichTextEditorValue").
I found it was happening as the existing value is provided to the
FromEditor
method of the property value converter, but the parsing doesn't expect to get the actual object here and only handles a JSON structure or the raw markup. So I've just added an initial check to the parsing, to see if we have the object of the right type already, and if so, return it.Testing