Per Nergård (MVP)
Dec 23, 2010
  4137
(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
Accelerating Optimizely CMS and Commerce upgrades with agentic AI (Part 2 of 2)

The Real Transformation in Optimizely CMS 13: Why the Upgrade Itself Is the Easy Part. A field-tested playbook for enterprise teams moving from...

Hung Le Hoang | May 18, 2026

Is the most powerful AI model really the best value?

Artificial Intelligence is already becoming part of everyday software development. Developers now use AI tools to generate code, write documentatio...

K Khan | May 16, 2026

Optimizely London Dev Meetup 2026

Well, everyone, it's that time of the year again, and we have another London Developer meet up coming for this summer. The date is set for the 2nd ...

Scott Reed | May 15, 2026

Building a Custom RAG for Optimizely Opal

How to design a standalone RAG service for documents that don't belong in Optimizely One, and expose it to Opal and other AI tools without coupling...

Michał Mitas | May 14, 2026 |

Building a Custom RAG for Optimizely Opal

Opal's built-in knowledge is limited to content inside Optimizely One. Here's how to design a custom RAG service for documents that live outside th...

Michał Mitas | May 14, 2026 |

Semantic Search - Deep Dive

Deep dive into semantic search with Optimizely Graph

Michał Mitas | May 14, 2026 |