Per Nergård (MVP)
+1
Dec 23, 2010
visibility 4216
star star star star star
(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

error Please login to comment.
Latest blogs
Copies vs. Connections: Modeling Content Areas for Multilingual Success

Starting With the Simple Question Most multilingual content modeling conversations start with a deceptively simple question from a client: "If we s...

Vipin Banka | Aug 23, 2026

Content Transfer coming to Optimizely SaaS CMS

Back in June I released Content Transfer on the Optimizely nuget feed – today I’m releasing version 1.0 , because we’ve had it running out in the...

Matt Pallatt | Aug 23, 2026

Improving Optimizely Product Information in LLM Tools

Tools like Claude Code can be great for working with Optimizely CMS, but when they index outdated or incomplete information about developing a...

Nicholas Sideras | Aug 21, 2026 |

How to Get a Bacpac Out of DXP (And Never Do It By Hand Again)

Every Optimizely DXP project eventually runs into the same task: getting production data onto a local machine so you can actually troubleshoot...

KennyG | Aug 20, 2026