You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A customer of ours managed to bring the "value" of the property in a state where it was similar to this:
value: [
{id:1234},
null,
{id:1234},
]
So somehow one of the items in the array was null.
This cause two things:
The datatype failed, because it tried to access the id property of a null object
The frontend failed because the value converter tried ti access properties on a null json object.
I have not been able to reproduce how the null got there in the first place, but it would be nice if the two scenarios above where more null tolerant :)
I fixed the datatype by adding a null check around the building of the renderModel:
I think I've seen this where the Back Office is slow to load. They click Save and Publish before the custom property editor has fully loaded and then NULLS are stored. I can't quite remember what site this was on buy I hope this helps... are they on an older Umbraco?
A customer of ours managed to bring the "value" of the property in a state where it was similar to this:
So somehow one of the items in the array was null.
This cause two things:
The datatype failed, because it tried to access the id property of a null object
The frontend failed because the value converter tried ti access properties on a null json object.
I have not been able to reproduce how the null got there in the first place, but it would be nice if the two scenarios above where more null tolerant :)
I fixed the datatype by adding a null check around the building of the renderModel:
The text was updated successfully, but these errors were encountered: