Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
This page describes how to configure a content app to be privacy-aware, for example in the context of GDPR regulations. The Contacts app, a Magnolia demo content app, is an example of an app adapted to comply with privacy regulations. An existing content app can be made privacy-aware almost on-the-fly. You just need to configure the app in accordance with the following guidelines.
Add mgnl:visitorReference to content node type
Please be aware that the
mgnl:visitorReference node type has a mandatory property called
visitorId. Without it you cannot save a
mgnl:visitorReference node. See below its definition in the Visitor manager submodule:
The Visitor manager submodule is where most of the configuration of the Privacy module is done.
Use a dedicated subapp class and field
In your app use a dedicated privacy-enabling subapp class and field(s). In the Contacts app this is done with the
info.magnolia.privacy.sample.contentapp.PrivacyAwareContactDetailSubapp class (line 1), the
visitorId field (from line 9). The field is linked to the
visitors repository (line 11), a dedicated repository which stores visitor consent information:
Lines 3 and 4 make sure the app (subapp) uses the newly defined node type. Because of MGNLPRIV-35 we actually don't set the
mgnl:privacyContact node type in the Detail subapp's definition decoration.
The field label "Visitor" is defined in the message bundle of the