Magnolia 6.0 reached end of life on June 26, 2019. This branch is no longer supported, see End-of-life policy.
The JCR browser app is a Magnolia tool that allows you to work at the repository level in any workspace. You can see details that are not readily visible in a specific app's tree view, and edit content and associated configuration.
The JCR app is based on the content app framework. The app is in the Tools app group that is only available to the
superuser role. This restriction is configured in the app launcher layout.
The app is configured in
You can edit and add content in any workspace, but always do this with caution because you are working a repository level.
The Configuration app is essentially a JCR browser that displays the
The JCR browser shows content as it is stored in the JCR and is useful for looking at details that you would not see in the Pages app.
Example: Comparison of Demo Travel's About page in the editor and JCR browser.
|About Magnolia Travels||String|
|Über Magnolia Travels||String|
|<p>We are a full serv ...</p>||String|
|<p>Wir sind eine una...</p>||String|
Nodes and properties:
Component properties are stored under the component node:
|Area properties, if any, reside under the area node.|
Page properties reside under the page node:
While in some cases the JCR browser may be considered a quicker alternative to editing content in a dedicated app, editing directly in the JCR browser rather than in the app may actually cause more damage than good to the integrity of your data.
There are certain things that you can do in the browser that are not possible in the editor. Here are a few suggestions:
While it is possible to move components from one page area to another, this is not a best practice. For seamless publishing your page content should always comply with the options in the template.
Publishing in the Website JCR browser is different from publishing in the Pages app: