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

error Please login to comment.

Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |

See all blogs