Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
Action is the common name for tasks such as copying, moving and deleting. You can perform actions on pages and other node types. Actions are available as buttons at the bottom of the AdminCentral page and in a context menu.
To select a node click on any of the elements in the row and it will be highlighted and remain selected until you select another. To deselect all, click Refresh.
The content in some columns can be changed in AdminCentral, for example the page name and title in Website and the URL and title in Documents.
To rename content:
Website content, documents, configuration and everything else is stored in the . Each item is stored in a node. The node name is generally displayed in the first column in AdminCentral, for example the page name in the
website workspace and document name in the
documents workspace. Besides being an internal reference to the node, the name is also used for various purposes such to create a page URL.
Character restrictions apply only to node names and not to other user-entered content. For example, you can only use certain characters in a page name but any character in the page title. When a disallowed character is used it is automatically substituted with a hyphen ( - ).
The Path Java class governs character restrictions. All alphanumeric characters (a-z, A-Z, 0-9), the hyphen ( - ) and the unscore ( _ ) are safe to use in node names. We recommend that you use lowercase letters separated by a hyphen.
JCR 2.0 specification defines the following invalid characters in a local name.
Forward slash (solidus)
Left square bracket
Right square bracket
Vertical line (pipe)
Node names are used to create URLs and cannot contain characters that are disallowed or have special meaning in URLs. These conventions are established by the Internet Engineering Task Force (IETF)) Network Working Group on URLs.
Unicode code point
Solidus (forward slash)
Number sign (pound, hash)
Characters disallowed by Magnolia.
Unicode code point
Apart from the exceptions above, Magnolia allows you to use the full UTF-8 character set for node names and other properties, but UTF-8 encoding is disabled by default. See for instructions on how to enable it. When enabled, all special characters and notations covered by the Unicode specification can also be used.
Starting with Magnolia 4.5, the dot character (full stop, Unicode 2E) can be used in node names with the single limitation that it cannot be the first character. You can create a user
john.smith, a page
article.one, a document
Magnolia-Flyer-4.0.pdf, a configuration node
The work area reloads automatically after most commands. The Refresh command is useful for example to deselect all nodes and to collapse all expanded trees simultaneously. When you click Refresh the work area reloads and only first-level nodes display.
Nodes can be duplicated in AdminCentral.
To copy a node:
Note the following about copying:
Nodes can be moved by dragging them to a new location.
To move a node:
Note the following about moving:
To delete a node:
Note the following about deleting:
Activation is the process of publishing data to the public instance. Nodes are copied from the author to the public instance. Once activated, they are available on the public instance.
Magnolia uses public-key cryptography to ensure the security of the activation process. For more information see Activation security.
The activation status is indicated in the Status column and there are three possibilities:
The screenshots below compare the page structures in Website on the author and public instances. Note in the public instance the absence of the un-activated pages and the entire Status column.
There are two activation commands:
In Website, Documents and Data the activation procedure depends on whether a workflow is set up in the installation. If this is the case, nodes are not activated immediately and an activation request is sent to the appropriate inbox for approval. In all other areas activation is immediate.
To activate a node:
Note that its is not possible to activate a child node (status = red) if the parent node is not activated (status = red). Where workflow is in place, after proceeding with publication, the work item is sent back to the Inbox with an error message indicating that the parent node needs to be activated first.
For more information see Workflow.
Files stored in Documents and data items stored in Data that are used by web pages are not automatically activated together with the page and need to activated individually.
De-activation is the process of un-publishing or removing data from the public instance. Nodes remain available on the author instance for future use and modification. When you de-activate a node, the status changes to red and the node is removed from the public instance. When you de-activate a parent node, the children are of necessity also de-activated.
Like activation, in Website, Documents and Data the de-activation procedure depends on whether a workflow is set up in the installation. If this is the case, nodes are not de-activated immediately and a de-activation request is sent to the appropriate inbox for approval. In all other areas de-activation is immediate.
To de-activate a node:
For more information see Workflow.
Besides the procedural differences, deletion and de-activation have different consequences. When a node is de-activated it remains available on the author instance for future use. When a node is deleted it is permanently removed from both instances.
Schedule page de-activating with caution. If you de-activate a parent page, you automatically de-activate all of the sub pages. Scheduled deactivation is best used for standalone pages or pages which have few dependencies.
When you need to revert a page back to its normal or default state after a period of publication with altered content, such as after a fixed-duration campaign, the best approach is not to deactivate the campaign page when the content is no longer relevant. Instead, restore the prior version of the page content in order to get back to the post-campaign state. Then activate the page, this time with the publication date set into the future. When the prior version is activated, the temporary campaign content is replaced automatically. There is no need to schedule a date for deactivation.
For example, you are running a promotion on a homepage for an offer of limited duration. When the promotion is over, you want the homepage to return to its pre-promotion appearance.
Single nodes and entire structures can be imported into and exported from most work areas. There are various ways to import and export data in Magnolia that are discussed in . This functionality is useful in many circumstances, for example when experimenting with different page structures and content, you can export the relevant node to XML and then delete it in Website. On import, the page structure and any content added to pages is recreated entirely. This function can also serve as an additional backup fail-safe.
The XML structure of exported file reflects the hierarchy of the data and the name of the file reflects the path. For example, if you export the entire contents of Website, the file will be named
website.xml, whereas the
demo-project/about/subsection-articles/article page will be named
To export a node:
To import a node:
Search is available in Website and Documents. The search box is located to the right of the command bar.
The search function is useful for locating specific content within your pages and files. The following is indexed for search:
Searching rules are:
Search results display in the search work area and the available options and procedures are discussed in.