Per Nergård (MVP)
Dec 23, 2010
  4096
(0 votes)

Custom properties doesn’t inherit base types settings class

Today I was playing around with custom properties and made my own version of the PropertyXhtmlString.

I wanted to disable some of the editor options so I clicked the “Custom Settings” tab for my custom property but to my surprise there wasn’t any settings available.

So it seems that if you do custom properties they don’t inherit the base type settings class.

It’s easy to fix though. In my case using the TinyMCE editor I had to add the following attribute to my custom property control class: [PropertySettings(typeof(TinyMCESettings), true)].

Dec 23, 2010

Comments

Please login to comment.
Latest blogs
Meet the latest OMVPs - H1 2026 Cohort

Meet the Latest Cohort of Optimizely Most Valuable Professionals (OMVPs) Every year, the Optimizely Most Valuable Professional (OMVP) program...

Satata Satez | Mar 13, 2026

Optimizely Commerce vs Composable Commerce: What Should You Do with CMS 13?

As organizations modernize their digital experience platforms, a common architectural question emerges: Should we continue using Optimizely Commerc...

Aniket | Mar 12, 2026

Missing Properties tool for Optimizely CMS

If you have been working with Optimizely CMS for a while you have probably accumulated some technical debt in your property definitions. When you...

Per Nergård (MVP) | Mar 10, 2026

AI Generated Optimizely Developer Newsletter

Updates in the Optimizely ecosystem are everywhere: blog posts, forums, release notes, NuGet packages, and documentation changes. This newsletter...

Allan Thraen | Mar 10, 2026 |