Per Nergård
Dec 23, 2010
  3359
(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
Optimizely SendGrid SMTP host is deprecated

SendGrid is a services for sending email that is included in Optimizely DXP. Previously smtp.episerver.net was the recommended SMTP server to use,...

Tomas Hensrud Gulla | Dec 4, 2022 | Syndicated blog

Hosting Optimizely CMS 12 on Docker Engine

Since Optimizely CMS can now be deployed as a Docker container, here is a demonstration of building, running and scaling an Optimizely CMS 12 site ...

Stefan Holm Olsen | Dec 4, 2022 | Syndicated blog

How to use CacheTagHelper with content areas in Optimizely CMS 12

I might be going out on a limb here - if you have a better solution, feel very free to share it!  Upgrading your Optimizely web application from .N...

Andreas J | Dec 2, 2022

The 1001st Piece in your 1000 Piece Puzzle: .NET Default Interface Functions

I was recently working with a client who wanted a reasonably large subsystem added to Optimizely that would add automated management to their...

Greg J | Nov 28, 2022 | Syndicated blog