CMS > CMS for administrators > Properties

Episerver CMS iconProperties

This topic is intended for administrators and developers with administration access rights in Episerver.

Properties are central in Episerver CMS. Content type properties store and present data, such as page types and block types, and they are fields where editors enter information into a page type. A property can be the page name, an image placeholder, or the editor area, where you can add text. For example, the XHTML editor is a property of the type XHTML String (>255), which results in an editorial area in the page type when used. For property content to be visible to visitors, link it to a content type with corresponding rendering.

Property types

You can define properties in code or from the administrative interface. For certain properties defined in code, you can create “non-breaking” changes in admin view to override these settings. If a property is defined in code and cannot be changed in admin view, information appears. If you make changes to a property defined in code, you can reset the changes to the values defined in code.

The following types of properties are used:

  • Built-in properties are set by the system and are automatically available for all pages and blocks regardless of type. For example, PageName (name of the web page) and PageStartPublish (start publish date for the page).
  • User-defined properties are added to the page or block type definition in code or from the admin view. Typical examples are Heading and MainBody.

You can locate property settings under the Config tab in the Property Configuration section, and under the Content Type tab when you work with content types.

Editing and adding properties on content types

A common example for editing properties is to define toolbar buttons for the TinyMCE rich-text editor. You normally define properties in code but occasionally add them in admin view, because properties added from there are not rendered.

When you edit and add properties, the following tabs are available:

  • Common Settings is where you edit a property's common settings.
  • Custom Settings depend on the property data type being editing.

Defining language-specific properties

When working with globalizationManaging content in multiple languages, and localizing the user interface., you define in every template which fields vary depending upon the language. To do this, set whether the property for that field should be “locked” or “open” for globalization. This is done using the Unique value per language setting in admin view.

Properties that have unique value per language are editable in all enabled languages on the website, which is normally the case. You can edit only properties that do not have language-specific values in the language in which the page was created (the original page language). These properties are disables in edit view with an icon indicating the original language.

Imagine the property defining the sort order field is not set as a unique value per language (that is, the Unique value per language check box is cleared). When creating a new page, you can set sort order in the original page language. But if you create a version of the page in another language, the sort order field is not editable. As a result, the sort order is the same for all enabled languages. If you want to change the sort order for each language, select the Unique value per language check box.

If a property is changed to not having a unique value, all existing values for that property are deleted. So if the property for the editor area is changed to not have a unique language, all text entered in the editor area for all languages on the website are permanently deleted.

Organizing properties in content

You can alter the order in which properties are displayed to editors in a page or block type. You can also move properties between tabs in a page type. These changes are done for each page type in admin view.

Configuring customized property settings

On the Config tab under Property Configuration > Edit Custom Property Types, you can configure custom property types.

back to top Episerver image

Help topics   Need help?   FAQs   Glossary   Site map   Videos

Episerver User Guide 17-1 | Released: 2017-02-07 | © Episerver 2017 | Send feedback to us