Per Nergård
Aug 19, 2010
(0 votes)

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


Please login to comment.
Latest blogs
Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog

New Optimizely certifications - register for beta testing before November 1st

In January 2023, Optimizely is making updates to the current versions of our certification exams to make sure that each exam covers the necessary...

Jamilia Buzurukova | Sep 28, 2022

Optimizely community meetup - Sept 29 (virtual + Melbourne)

Super excited to be presenting this Thursday the 29th of September at the Optimizely community meetup. For the full details and RSVP's see the...

Ynze | Sep 27, 2022 | Syndicated blog

Preview multiple Visitor Groups directly while browsing your Optimizely site

Visitor groups are great - it's an easy way to add personalization towards market segments to your site. But it does come with it's own set of...

Allan Thraen | Sep 26, 2022 | Syndicated blog