Element views allow to group (elements of) resource types for editing them in the page editor. If more than one (non-empty) element view is available, the user can choose the view and dependent on that view, he can add, edit and move elements of different resource types a page.

Element views are in particular useful to

  • allow to edit content in nested containers where edit points may overlap,
  • get a better overview on the available content elements by grouping them task-specific,
  • control access to elements of specific type dependent on roles, group memberships or user permissions.

Defining an element view

Element views are resources of type elementview. Typically element views are defined in modules that expose the resources types that should be shown in an element view. By convention, element views are stored in a subfolder elementviews/ of the module folder. When an element view content is defined, it automatically makes up an element view, selectable in all resource type configurations and (if non-empty and accessible to the current user) selectable in the page editor.

1.1 Creating an element view content

To create a new element view:

  • Open the explorer view of the traditional workplace.
  • Choose in which module the element view should be defined and (create and) move to the subfolder elementviews/ of this module.
  • Choose the "New wizard" and select "Other options" -> "Element view".
  • Choose a filename (typically with suffix .xml) and edit the metadata.

1.2 Editing the element view content

The element view content stores mainly the name of the view used when the view is displayed in the page editor's context menu. Moreover you can alter the display order.

Fig. [elementview_content]: Element view content
Content fields of the element view content

The title is mapped to the Title property and used as name of the view in the page editor, if no title key is given.

Title key

A key from a workplace message bundle to show a localized name of the element view in the page editor. Provide only the rare key, e.g., myelementview.title.

Display order

Non-negative integer value to specify the display order relative to other element views. Element views with smaller numbers are displayed earlier.

1.3 Setting permissions in the element view content

By setting permissions on the element view content, you can determine who is allowed to see the view. Only users with permissions on the elementview content get the view displayed for selection in the page editor.

Interesting details on element views

2.1 Which element views can I choose via the page editor?

Element views can be added by modules. Thus, many different element views may exist, but you may not want to show all of them to all users.

Thus, element views can only be selected via the page editor if:

  • The user has permissions to see the element view at all.
  • The view is non-empty for the current page, i.e., at least one resource type is configured to be in the view via the sitemap or module configurationAnd the user has the rights to see resources of this type.

2.2 How are element views identified?

Element views are identified via the structure id of the element view content. Thus, element views with equal names imported via different modules will not conflict. The default view plays a special role. It has no content and is identified via the null id.

2.3 Which element view is chosen by default?

Element views are sorted by their display order. From the views that can be chosen, i.e., the non-empty views where the user has sufficient permissions to access them, a view with the smallest display order is chosen as default. Typically, if not empty, the default view is chosen by default.

If a user once selected a view, this view is kept - at least as long as it can be chosen.

2.4 How can I get and set the element view automatically?

The current view is stored in the session cache, i.e., in CmsADESessionCache. The class provides the according getter and setter.