Per Nergård (MVP)
+1
Nov 26, 2010
visibility 5108
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
Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |