Take the community feedback survey now.

Per Nergård (MVP)
Oct 5, 2012
  2469
(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
Content modeling for beginners

  Introduction Learning by Doing – Optimizely Build Series  is a YouTube series where I am building  a fictional  website called  TasteTrail , food...

Ratish | Sep 14, 2025 |

A day in the life of an Optimizely OMVP - Enhancing Search Relevance with Optimizely Graph: Synonyms and Pinned Results

When building search experiences for modern digital platforms, relevance is everything. Users expect search to understand their intent, even when...

Graham Carr | Sep 14, 2025

Optimizely CMS and HTML validation message: Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

When using the W3C Markup Validation Service, some annoying information messages pop up because Optimizely CMS adds the trailing slash to...

Tomas Hensrud Gulla | Sep 14, 2025 |

Turbocharge your strings - a case of display channels

When doing a routine performance test, during a CMS 12 upgrade, I was able to achieve 95% performance improvement. Let's look at SearchValues with ...

Stefan Holm Olsen | Sep 14, 2025 |