Calling all developers! We invite you to provide your input on Feature Experimentation by completing this brief survey.

 

Per Nergård
Aug 19, 2010
  5132
(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

Comments

Please login to comment.
Latest blogs
Level Up with Optimizely's Newly Relaunched Certifications!

We're thrilled to announce the relaunch of our Optimizely Certifications—designed to help partners, customers, and developers redefine what it mean...

Satata Satez | Jan 14, 2025

Introducing AI Assistance for DBLocalizationProvider

The LocalizationProvider for Optimizely has long been a powerful tool for enhancing the localization capabilities of Optimizely CMS. Designed to ma...

Luc Gosso (MVP) | Jan 14, 2025 | Syndicated blog

Order tabs with drag and drop - Blazor

I have started to play around a little with Blazor and the best way to learn is to reimplement some old stuff for CMS12. So I took a look at my old...

Per Nergård | Jan 14, 2025

Product Recommendations - Common Pitfalls

With the added freedom and flexibility that the release of the self-service widgets feature for Product Recommendations provides you as...

Dylan Walker | Jan 14, 2025