Don't miss out Virtual Happy Hour today (April 26).

Try our conversational search powered by Generative AI!

Per Nergård
Oct 5, 2012
  2277
(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
Azure AI Language – Extractive Summarisation in Optimizely CMS

In this article, I demonstrate how extractive summarisation, provided by the Azure AI Language platform, can be leveraged to produce a set of summa...

Anil Patel | Apr 26, 2024 | Syndicated blog

Optimizely Unit Testing Using CmsContentScaffolding Package

Introduction Unit tests shouldn't be created just for business logic, but also for the content and rules defined for content creation (available...

MilosR | Apr 26, 2024

Solving the mystery of high memory usage

Sometimes, my work is easy, the problem could be resolved with one look (when I’m lucky enough to look at where it needs to be looked, just like th...

Quan Mai | Apr 22, 2024 | Syndicated blog

Search & Navigation reporting improvements

From version 16.1.0 there are some updates on the statistics pages: Add pagination to search phrase list Allows choosing a custom date range to get...

Phong | Apr 22, 2024