A critical vulnerability was discovered in React Server Components (Next.js). Our Systems Remain Fully Protected. Learn More

Per Nergård (MVP)
Nov 26, 2010
  4920
(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
Jhoose Security Modules v2.6.0 — Added support for Permissions Policy and .NET 10

Version 2.6.0 adds Permissions Policy header support, updates to .NET 10, improved policy management, configurable security settings, and enhanced...

Andrew Markham | Dec 6, 2025 |

Building a 360° Customer Profile With AI: How Opal + Optimizely Unlock Predictive Personalization

Creating truly relevant customer experiences requires more than collecting data—it requires understanding it. Most organizations already have rich...

Sujit Senapati | Dec 4, 2025

Building a Lightweight Optimizely SaaS CMS Solution with 11ty

Modern web development often requires striking a difficult balance between site performance and the flexibility needed by content editors. To addre...

Minesh Shah (Netcel) | Dec 3, 2025

Creating Opal Tools Using The C# SDK

Over the last few months, my colleagues at Netcel and I have partaken in two different challenge events organised by Optimizely and centered around...

Mark Stott | Dec 3, 2025