Mark Everard

Hello, I'm Mark – a PhD physicist turned technologist / architect.

Archive for April, 2013

Configuring TinyMCE using EPiServer custom property settings

without comments

The TinyMCE rich-text editor provides great flexibility for editors to create and mark-up content within EPiServer. TinyMCE is a seemingly infinitely configurable tool and can be configured to show / hide many of its available features.  One of the ways EPiServer Administrators / Developers / Integrators can help is by configuring TinyMCE to only show features that are necessary in a given context.

This posts demonstrates how to modify TinyMCE either globally or on a property by property basis using custom property settings.

Property Settings

Property Settings are not a new feature. They were introduced in CMS 6 and are used to store settings for page properties. They are editable from within the Admin mode. One of the primary uses of this feature is to configure settings and buttons that are shown to editors when using the TinyMCE text-editor. Property settings can also usefully be used to provide editor managed drop-down lists.

TinyMCE custom property settings

You can specify which buttons to use for each XHTML property instance on a defined page type. This can be managed in Admin mode in the following way.

  1. Go into EPiServer Admin mode
  2. Navigate to the Page Type tab and to the specific Page Type you want to modify.
  3. Pick the XHTML property you wish to add custom settings
  4. Click the Custom Settings tab

You should now see the following interface:

property settings interface

You can use this to either define a custom setting that will be applied to this instance, or define a new global setting that will be used by default.

The TinyMCE toolbar can be edited by dragging and dropping buttons from the inactive tools to the editor toolbar area. You can adjust the position of existing feature buttons and the overall layout of your toolbar.

CustomPropertySettingEditorToolbar

Global settings

Defining custom settings for each XHTML property on every page type will; for any reasonably sized EPiServer installation be a very time-consuming task. It is likely that you will have a set of common TinyMCE configurations that you wish to apply and share between different properties across different page types. These can be managed by creating them as a global property setting, and adding some additional meta data such as a name and description. Global settings can then be selected on each property that you wish to use them for.

Default settings

Any XHTML property that does not have a  custom property setting will use the default EPiServer XHTML property setting, meaning the TinyMCE toolbar will display will a pretty full list of feature buttons and settings. The default option can be changed to any one of your defined global property settings. This allows you to apply settings across the board. This is useful for modifying any TinyMCE instances that appear in DynamicContent controls.

propertysetting-globaldefault

Written by mark

April 17th, 2013 at 12:19 pm

Posted in EPiServer

EPiServer CMS 7 logical architecture diagram

with 3 comments

I often have to describe the logical components of EPiServer CMS to clients and customers. It always feel like I end up recreating a logical architecture diagram on each occasion.

The best place to keep something so that you never lose it, is in a place where it’s easy to find. Anything on the web is easy to find (thanks Google). I’ve decided the best place to keep the following EPiServer CMS7 logical architecture diagram is out in the open.

EPiServer CMS7 logical architecture

The added benefit of this for everybody else, is that I’m happy for you to use my work. If any of you are LucidChart users then I’m happy to share the original with you so that you can apply any further modifications.

Written by mark

April 4th, 2013 at 10:30 am

Posted in EPiServer