Per Nergård (MVP)
OMVPSaaS CMS Developer CertificationCommerce Connect 13 Developer Certification +2
Nov 26, 2010
visibility 5223
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
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026