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.

Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |

See all blogs