Magnolia Content Dependencies module provides functionality to track dependent content used by web pages. Dependent content includes other Web pages and DMS assets. Information and alerts are provided when activating or deleting a page that has a dependency on other content and when deleting a page or asset on which another page depends.
Although the Standard Templating Kit would not render broken links on the public instance, this functionality provides all the necessary information about the consequences of an activation or deletion.
Content Dependencies is an enterprise module included in the Enterprise Edition bundle and typically already installed. Go to Magnolia Store > Installed modules in AdminCentral to check. To install the module individually, see the general module installation instructions.
See the general module uninstalling instructions and advice.
The Content Dependencies module requires no configuration.
On installation, the module creates the following configuration at Configuration >
Classes and what they do:
DefaultDependenciescompares content instances based on their handle.
DefaultDependencyKeepingNodeDataFinderdelivers a set of NodeData that keeps references based on the NodeData's name.
DependenciesDialogControlis a FreeMarker control that prints dependencies from the
dmsrepositories in the current content and shows the activation status. (See STK). Also used to resolve content from workflow items. (See Workflow module)
In the STK, the Content Dependencies module includes a generic
tabDependencies dialog definition, accessible at Templating Kit > Dialog Definitions >
/generic/pages/tabDependencies. This definition uses the
dependenciesControl control type registered by the module. See Configuration above.
This generic tab configuration is included in all page properties dialog definitions which are included by
mainBar on all STK templates. The page properties dialogs are configured at Templating Kit > Dialog Definition >
Open any page in Website and click Page Info in
mainBar to view the
tabDependencies tab. The screenshot below is of the
stkHomeProperties dialog on the
/demo-project page. Both the status indicator and path of the dependent content are included.
In the Workflow module configuration, the Content Dependencies module adds the
tabDependencies tab to the
editActivationWorkItem dialog definition, accessible at Configuration >
In Inbox, when you click Edit Workitem, the
editActivationWorkItem dialog opens and the
tabDependencies tab lists the status indicator and path of the dependent content. The screenshot below shows the dialog when requesting activation of the
The Content Dependencies module includes
ReferencesHtmlServlet in the filter chain. This configuration is at Configuration >
/server/filters/servlets/ReferencesHtmlServlet. It registers the
DepencenciesServlet Java class that renders the list of dependencies in the warning message displayed when deleting a page in Website or file in Documents.
When you delete and page or file the warning dialog lists the dependent content.