Per Nergård (MVP)
+2
Nov 26, 2010
visibility 5197
star star star star star
(0 votes)

Property changed type when updating from 5.1 to 6

A couple of weeks ago we upgraded an old 5.1 site to CMS 6. We got a strange error where the rendered content of one page got messed up.

After some investigation we found that a property had got it’s type changed from XhtmlString to Longstring and changing it back to xhtml fixed the rendering.

We didn’t find any other property that had changed type nor did we find any explanation to why this happened.

So when migrating from CMS 5.1 to CMS 6 I guess that a quick check that all of the properties types are still the same is a good idea.

Nov 26, 2010

Comments

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |