CMS for administrators > Properties

Properties

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

Properties are central in Episerver CMS. Properties are used in content types to store and present data, such as page types and block types, and they are the “fields” where editors enter information into a page type. A property can be for instance the page name, an image placeholder, or the editor area, where text can be added. 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, it must be linked to a content type with corresponding rendering.

Property types

Properties can be defined either in code or from the administrative interface. For certain properties defined in code, it is possible to do “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 about this will be displayed. If you make changes to a property defined in code, it is possible to 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.
  • Dynamic properties are set on page level and inherited by child pages.

Property settings can be found under the Config tab in the Property Configuration section, and when working with content types under the Content Type tab.

Editing and adding properties on content types

A common example of property editing is to define toolbar buttons for the TinyMCE rich-text editor. Properties are normally defined in code but rarely added in admin view, since properties added from there are not rendered.

When editing and adding 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 languages enabled on the website, which is normally the case. Properties that do not have language-specific values can only be edited in the language in which the page was created (the original page language). These properties are grayed out 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 not selected). 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. This means that 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

Under Property Configuration and Edit Custom Property Types and Dynamic Properties, you can configure custom property types.

back to top




Episerver User Guide update 15-5 | Released: 2015-11-16 | Copyright © Episerver AB | Send feedback to us