Per Nergård (MVP)
Nov 26, 2010
  4956
(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

Please login to comment.
Latest blogs
AEO/GEO: A practical guide

Search changed. People ask AI tools. AI answers. Your content must be understandable, citable, and accessible to both humans and machines. That’s...

Naveed Ul-Haq | Feb 17, 2026 |

We Cloned Our Best Analyst with AI: How Our Opal Hackathon Grand Prize Winner is Changing Experimentation

Every experimentation team knows the feeling. You have a backlog of experiment ideas, but progress is bottlenecked by one critical team member, the...

Polly Walton | Feb 16, 2026

Architecting AI in Optimizely CMS: When to Use Opal vs Custom Integration

AI is rapidly becoming a core capability in modern digital experience platforms. As developers working with Optimizely CMS 12 (.NET Core), the real...

Keshav Dave | Feb 15, 2026

Reducing Web Experimentation MAU Using the REST API

Overview Optimizely Web Experimentation counts an MAU based upon the script snippet rendering for evauluation of web experiement. Therefore when yo...

Scott Reed | Feb 13, 2026