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

 

Per Nergård
Oct 5, 2012
  2358
(0 votes)

Bug in CMS6 OPE using EPiServer:Property

The other day we got a report of an error when using OPE (on page editing) in a CMS6 site. The editors were able to edit the page but when saving an error occurred: “unable to save”XX” because property is read only”.

After a quick check what could cause the error we pinpointed it to a user control containing a single EPiServer.Property with it’s PageLinkProperty set.

Ok so now we knew where but not why. I had no clue so I just tried to set the EPiServer.property PageLink instead of using the PageLinkProperty. I really didn’t expect anything but to my surprise after the change the property was not longer editable via OPE.

EPiServer support has confirmed this as a bug and the expected behavior of setting the PageLinkProperty should be the same as using the PageLink.

Oct 05, 2012

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