Saving a media-type with a rich-text property breaks the save media button

[mdeslauriers-sigmund]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

13.2.2

Bug summary

Adding a property with the "Rich text" data-type to the "Image" media-type, cause a javascript error when the user create a new image in the media library. The save operation on the back-end seems successful, but the save button on the front-end keeps spinning and never return to its original state.

Specifics

Reproduced in Chrome and Firefox

The error occurs in the Media library, in the "Create Image Form" /umbraco#/media/media/edit/-1?doctype=Image&create=true

The spinner never resets:

The javascript console error is : modelObject is undefined:

Note : It also can be reproduced in the "Edit Image Form" if the richtext property is empty on the initial load.

Steps to reproduce

Modify de Media type

• Go to the "Settings" section
• Expand "Media Types" and select "Image"
• Add a new property using the "Ricktext editor"
• Click the save button

Create a new image

• Go to the "Media" section
• Right click on the Media tree an select "Create" -> "Image"
  • 
• Enter a node name
• Select an image
• Click the save button

The error occurs here:

• The spinner on the save button is stuck
• A javascript error is visible in the console
• A full page refresh will show that the image was created

Expected result / actual result

Actual result :

• The spinner on the button is stuck
• A javascript error is visible in the console

Expected result :

• The save button should return to its initial state
• No javascript error shloud be visible in the console

[github-actions[bot]]

Hi there @mdeslauriers-sigmund!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face:

[nhudinh0309]

Hi @mdeslauriers-sigmund, Thanks for reporting this issue! I was able to reproduce it on version 13.2.2, 13.2.1 and 13.3.0. But for me, the JS console shown as below:

I also tested on version 12.3.9 and the save function works without any problem. So this is a regression issue. I will go ahead and mark it as a sprint-candidate 😄