A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Per Nergård (MVP)
Dec 23, 2010
  3017
(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
A day in the life of an Optimizely OMVP: Learning Optimizely Just Got Easier: Introducing the Optimizely Learning Centre

On the back of my last post about the Opti Graph Learning Centre, I am now happy to announce a revamped interactive learning platform that makes...

Graham Carr | Jan 31, 2026

Scheduled job for deleting content types and all related content

In my previous blog post which was about getting an overview of your sites content https://world.optimizely.com/blogs/Per-Nergard/Dates/2026/1/sche...

Per Nergård (MVP) | Jan 30, 2026

Working With Applications in Optimizely CMS 13

💡 Note:  The following content has been written based on Optimizely CMS 13 Preview 2 and may not accurately reflect the final release version. As...

Mark Stott | Jan 30, 2026

Experimentation at Speed Using Optimizely Opal and Web Experimentation

If you are working in experimentation, you will know that speed matters. The quicker you can go from idea to implementation, the faster you can...

Minesh Shah (Netcel) | Jan 30, 2026