Upgrading Umbraco 13.10.1 → 17.5.3. After migration, some Block Grid Settings fields (e.g. “CSS Classes”, “Custom CSS”) show empty in the back office, even though the old data is still in the DB — just in the wrong shape.
v13 (before):
"settingsData": [{
"contentTypeKey": "9860e8fc-2346-42d6-a70c-cd8f7be0609f",
"udi": "umb://element/90859e4cd6294483b2c1f3a6c757b634",
"cssClasses": "text-xl",
"backgroundImage": "[]",
"blockID": null,
"customCSS": null
}]
v17 as-migrated (actual, broken):
"settingsData": [{
"contentTypeKey": "9860e8fc-2346-42d6-a70c-cd8f7be0609f",
"key": "90859e4c-d629-4483-b2c1-f3a6c757b634",
"values": [],
"cssClasses": "text-xl",
"backgroundImage": "[]",
"blockID": null,
"customCSS": null
}]
udi was converted to key and the new values container was added, but cssClasses (and the other settings) were left behind in their old flat fields instead of being moved into values. The editor only reads from values, so the field shows blank/lost even though "text-xl" is sitting right there.
v17 expected shape:
"settingsData": [{
"contentTypeKey": "9860e8fc-2346-42d6-a70c-cd8f7be0609f",
"key": "90859e4c-d629-4483-b2c1-f3a6c757b634",
"values": [
{"editorAlias": "Umbraco.TextBox", "culture": null, "segment": null, "alias": "cssClasses", "value": "text-xl"}
],
"cssClasses": "text-xl",
"backgroundImage": "[]",
"blockID": null,
"customCSS": null
}]
(We reconstructed this “expected” shape by editing the same block by hand in v17 and checking what Umbraco itself writes — it keeps the old flat fields in place untouched, but the only thing actually read is the matching entry in values.)
Questions:
- Has anyone else seen this or is there a fix Available?