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.
Autogeneration creates components inside an area automatically, without editor involvement. Anything you define inside the
content item will be autogenerated.
Autogenerated components behave different from normal components:
- Ordered as defined: In an empty area, components are autogenerated in the same order as they are defined in the area definition.
- New components are placed last: If an area already has autogenerated components, newly defined components will be placed last.
- Cannot delete permanently: When you delete autogenerated component, it is regenerated and placed last in the area.
Configure component autogeneration in an area definition, under the
autoGeneration item. Simple example:
Parent item for autogenerated content. Put everything you want to autogenerate inside this item.
Component ID in
required , default is
A generator creates nodes based on the definition. The default
$webResourceManager.requireResource("info.magnolia.sys.confluence.artifact-info-plugin:javadoc-resource-macro-resources") CopyGeneratorcreates a copy of the exact nodes and properties you define under the