Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

We highly recommend using the same rootPath in both the detail and browser sub-apps, to benefit from our standard set of actions provided out of the box.

...

Browser subapp

A JCR content connector definition introduces properties that identify a JCR workspace as a data source. It also defines the node types to operate on.

...

nodeTypes

required

List of node types the content connector operates on. For example, the connector in the Contacts app displays contacts and folders.

<node‑type‑name>

required

Arbitrary node name such as contact if you are displaying contacts in the browser.

name

required

Node type the connector operates on. These are Magnolia or JCR node types such as  mgnl:contact.

icon

optional , default is none

CSS class name of the icon displayed on the workbench. See the default icons that ship with Magnolia or create your own.

strict

optional

Specifies whether to include only the exact node type and ignore subtypes. 

hideInList

optional

Specifies whether to display the current node in list view. Use this property to, for example, exclude folders.

workspace

required

workspace in the magnolia repository that you want to browse.

defaultOrder

optional

Default sort order for the content items in list views. The value is the name of the property you want to sort by, such as jcrName.

includeProperties

optional, default is false

Displays also the JCR properties of the node when set to true. Only nodes and subnodes are displayed when false.

includeSystemNodes

optional , default is false

Displays also nodes used by the system such as nodes internal to the operations of the JCR implementation. Set to true if you want to see image renditions in the imaging workspace for example.

rootPath

optional , default is / (root)

Path configured as the root of the workspace. Only content below the path is operated on.

...

Detail subapp

The connect definition for a detail subapp is much simpler. You only need to define the workspace.  

...