Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
AdminCentral is a Magnolia user interface for performing site management and configuration tasks. This is where administrators and editors work. Watch a video to get started.
AdminCentral is laid out in three areas:
Because AdminCentral is implemented in the Admin Interface module, the menu is configured in the module's configuration. There is a shortcut to the menu configuration in the Configuration > Menu. Each node under the
menu node represents a menu item that can be customized by changing the configuration properties.
The default menus are:
AdminCentral is configurable. You can hide menus and move them around to promote often-used items. By default, Magnolia ships with roles such as
superuser can see all menus, editors and publishers see only those that are relevant to their tasks.
Here is an example of AdminCentral with limited menus displayed to user
eric who belongs in an editor role.
A menu item can be configured with four parameters (properties):
Basename of the resource bundle with translations of the label.
Key for translation of the label. The key will be used as label if no translation is available.
Path to the menu item's icon.
MgnlAdminCentral.showTree displays a tree in the content area. If a path is passed, then the node addressed by that path will be opened in the tree.
Magnolia provides prepared trees for the most important repositories:
website-jcrwhich is a detailed view in the JCR structure of the
MgnlAdminCentral.showContent you can pass a URL to a web page or a path to content (without servlet context). The page will then be displayed in the content area. Examples:
If you create sub nodes under a menu item, the sub nodes will be organized in groups under that menu item. Menu groups can be identified in the menu by the arrow on the right side of the menu entry
When clicked, the group opens and all the child menu actions will be visible. If you specify an
onclick action, this action will be executed as well.
To add a customized context menu item:
prepareContextMenu method in a class that extends
Add a ContextMenuItem for the new menu item.
Each tree in AdminCentral, as well as trees included in modules, have a tree configuration class. For example, the
website tree has
, the tree in the Forum module has
ForumTreeConfiguration, and the tree in Data module has
Here is a snippet from
WebsiteTreeConfiguration. The action taken is
mgnlTreeMenuItemOpen. It is a function in contextmenu.js which is the function invoked when the
menuOpen context menu is clicked.
Another example, this time from the Forum module. The tree is configured in
mgnl.forum.TreeHelper is defined in
src/main/resources/mgnl-rsources/js-classes/mgnl/forum/TreeHelper.js in the Forum module and
name is a function in that class. Here's an example of one of
lockForum that gets passed to the
executeCommand is a command. The command's class is set to the class that is invoked when
executeCommand is invoked. In this case when
lockForum is passed to
executeCommand, the class
LockForumCommand is invoked. Command classes extend
Error and warning messages are displayed in a dialog on top of the page.
If you attempt to perform an action that is not possible, for example moving a node to an inappropriate location, an error is displayed. To close the dialog and return to the work area click OK.
When you perform an action that has serious consequences, for example deleting a node, a warning dialog is displayed. To close the warning and return to the work area, click either OK to proceed or Cancel.
The currently logged-in user's username is displayed in the top right corner. Click it to edit the account.
Standard users such as editors and publishers have limited access to their accounts. They can only modify the basics: name, password, email and language preference. They cannot modify permissions. Permissions are only visible to the superuser role by default. For more information see Security.
The search box in the bottom right allows you to search the content of your pages. Page names, titles, content, keywords and descriptions are indexed for search.
Search results are displayed in a list. The gray panel on the right offers grouping and sorting options. Click User, Name or Title to group and sort the results.
Two commands are available in the results list:
You can use your browser Back button to switch between the search results and the site hierarchy.