Per Nergård (MVP)
Oct 5, 2012
  2634
(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
Commerce 15 and CMS 13: Optimizely’s Next Step Toward AI-Powered, Graph-First Commerce

Optimizely is preparing to release Commerce 15 in mid-May 2026 , positioning this as a foundational shift—not just an upgrade. The direction is...

Augusto Davalos | May 7, 2026

The future of Content: Introducing Optimizely CMS 13

Optimizely In the rapidly evolving landscape of digital experience, the "monolithic vs. headless" debate is being replaced by a more sophisticated...

Aniket | May 6, 2026

Hide built in scheduled job from the admin UI

Ok so this probably goes into the not so useful section but late last night I got a veery strong feeling that all projects I am  involved with have...

Per Nergård (MVP) | May 6, 2026

Optimizely CMS 11 Is Out of Support — and the Hard Part of the Upgrade Isn't the CMS

On 10 April 2026, Optimizely formally announced that CMS 11 was out of support — CMS 13 had reached GA on 31 March, and by policy only the two most...

Allan Thraen | May 6, 2026 |