U4-10372 - Changing a datatype from MediaPicker2 to ImageCropper causes incompatible data in your property

Created by Claus Jensen 31 Aug 2017, 08:40:27 Updated by Sebastiaan Janssen 22 Feb 2018, 16:07:12

Relates to: U4-9295

Subtask of: U4-9609

We do not clear property data when switching the datatype of a property. This is fine for most scenarios (like changing a textbox to a RTE actually retains whatever value you had in your textbox to now be in the RTE).

This however doesn't work when going from a MediaPicker2 (storing a umb://media/whatever) to a ImageCropper expecting null or a json object containing ImageCropper data.

Since the ImageCropper doesn't handle this, it is now basically completely incapable of doing anything and you will get errors no matter what you do (trying to save empty and saving with new image doesn't fix the corrupt data).

The ImageCropper should be more tolerant and have checks to prevent simply failing to do anything if it's being served corrupt data.

Preferably it should handle cases where the data is a media udi and simply wrap it inside a real imagecropper object - since it isn't really a uncommon scenario to switch from the MediaPicker2 to a ImageCropper when you find out that you need this instead.

Comments