DOPE and Longstring property bug

The other day a colleague of mine got a report from a customer that when trying to use DOPE on certain pages an exception was thrown.

First I thought that it was a problem with a custom property but after viewing the code for the page type which was real simple, that it was a

<EPiServer:Propertye PropertyeName=”longstringproperty” /> that caused the problem.

Changing the property type to Xhtmlstring solved the problem.

This has been confirmed by EPiServer as a bug.

Aug 19, 2010

Comments

error Please login to comment.

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

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

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

See all blogs