JCR Browser app

The JCR Browser app is a Magnolia tool that allows you to work at the repository level in any workspace. You can see details not readily visible in a specific app’s tree view and edit content and associated configuration.

Configuration

The JCR Browser app is in the JCR Tools app group and is only available to the superuser role. This restriction is configured in the App launcher layout.

The app is configured in /jcr-browser/apps/jcr-browser-app.yaml.

Using the app

Be careful when editing and adding content in any workspace because you work at the repository level.

  • Searching and filtering:

    • Switch between workspaces using the Workspace filter. All workspaces are available. If you create a new workspace, it’s automatically available in the app.

      Switching between workspaces

  • Filter by Status:

    • Draft

    • Marked for deletion

    • Modified

    • Published

  • Display system properties: Select the checkbox to display properties such as UUIDs, creation dates, and user information. System properties are hidden by default. When displayed, you can’t edit them.

Display system properties checkbox marked

  • Editing: You can work with all content, except system properties, in the same way as in any other app.

Editing content directly in the JCR browser rather than in a dedicated app may damage the integrity of your data. Don’t move nodes (such as components from one page area to another), as the dedicated app might apply additional constraints to the move operation. Publishing in the JCR browser might differ from publishing in a dedicated app because different rules might apply for including subnodes.

JCR system properties

JCR defines standard application node types. You can set whether or not JCR properties are shown in a JCR data source definition. You can also make them visible in the JCR app if you want to see them.

Property Description

jcr:created

The date when the node was created. This is automatically created.

Each node’s creation date is registered through this property of the JCR primary node type nt:version.

jcr:createdBy

Who (or what) created the node.

jcr:primaryType

The base primary node type. This is automatically created.

jcr:uuid

A mandatory, protected STRING that exposes the node identifier.

jcr:title

The title of a node.
For more information about JCR system properties, go to 3.7.11 Standard Application Node Types.

Example website JCR browser

The JCR browser shows content as it is stored in the JCR and helps look at details that you wouldn’t see in the Pages app.

Example: Compare the Travel Demo’s About page in the JCR browser and in the editor.

  • JCR Browser

  • Editor

Node name Value Type

πŸ“ about

mgnl:page

     βΈ¬ main

mgnl:area

         βΈ¬ 00

mgnl:component

             ⬩ headline

About Magnolia Travels

String

             ⬩ headlineLevel

small

String

             ⬩ headline_de

Über Magnolia Travels

String

             ⬩ imagePosition

below

String

             ⬩ text

<p>We are a full serv …​</p>

String

             ⬩ text_de

<p>Wir sind eine una…​</p>

String

         βΈ¬ 04

mgnl:component

             βΈ¬ column1

mgnl:area

                 βΈ¬ 0

mgnl:component

             βΈ¬ column2

mgnl:area

                 βΈ¬ 03

mgnl:component

                     ⬩ headline

Learn more

String

                     ⬩ headlineLevel

medium

String

                     ⬩ headline_de

Mehr erfahren

String

                     ⬩ imagePosition

below

String

                 βΈ¬ 00

mgnl:component

                 βΈ¬ 01

mgnl:component

                 βΈ¬ 02

mgnl:component

                 ⬩ layout

8x4

String

     βΈ¬ footer

mgnl:area

…​.

     ⬩ hideInNav

false

Boolean

     ⬩ title

About

String

     ⬩ title_de

Über uns

String

Travel Demo’s About page in the editor

Property Description

<page folders>

Pages (mgnl:page) are stored in folders:

  • The page folder structure matches the website tree structure.

  • There are content nodes for each page area.

  • All area nodes reside at the same level, whether configured as main or nested areas.

     <area nodes>

Areas (mgnl:area) are stored in content nodes:

  • single and list areas have component subnodes.

  • noComponent areas can be used in various ways but typically have only area properties.

         <component nodes>

Components (mgnl:component) are stored in numbered content nodes:

  • Node numbers are sequential and assigned automatically.

  • Nodes are displayed in the same order as on the page.

  • The assigned number depends on when the component was created. The rendering order may not match the numbering order.

  • Components with nested components follow the same structure as area nodes. See component definition.

             <component properties>

Component properties are stored under the component node:

  • Property names correspond to dialog field names.

  • i18n properties have a locale suffix by default.

         <area properties>

Area properties, if any, reside under the area node.

     <page properties>

Page properties reside under the page node:

  • Property names typically correspond to field names in the Page properties dialog.

  • Components or areas can also add page-level properties.
Feedback

DX Core

×

Location

This widget lets you know where you are on the docs site.

You are currently perusing through the DX Core docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules