Page History
...
An XML file is added to the bootstrap directory. See Setting the bootstrap See Bootstrap directory.
Example : Addwebsite.travel.about.careers.cruise-manager.xmlto/magnoliaAuthor/data.Code Block language text └─<magnoliaAuthor> └─data └─website.travel.about.careers.cruise-manager.xml
A message is logged to the user:
Code Block language text 2019-03-28 14:27:06,676 INFO gnolia.content.observer.TaskCreatorWatcherCallback: File change detected at '/magnoliaAuthor/data/website.travel.about.careers.cruise-manager.xml', pulse task has been sent.
- A task is sent to the Tasks app.
Example: Import request task and Import action forcruise-managerpage in the Tasks app.
superuserassigns himself the task and clicks Import to import the content into the corresponding workspace in the repository. He can also Reject or Abort the import.
- The bootstrapped content is available in the relevant app.
Example: Cruise Manager page in the Pages app.
- The bootstrap directory is monitored and a new task sent to the Tasks app when a change in the XML is detected.
| Note |
|---|
|
Bootstrapping settings
You can use the Server configuration page in the About app to check the current bootstrapping settings.
Bootstrap directory
To set the bootstrap directory, add the magnolia.content.bootstrap.dir property in the magnolia.properties file. The bootstrap directory can reside anywhere on the file system and can be named anything you like.
...
| Code Block | ||
|---|---|---|
| ||
# The directory to expose file system resources from
magnolia.resources.dir=${magnolia.home}/modules
......
# The directory to import file system XMLcontent files from
magnolia.content.bootstrap.dir=${magnolia.resources.dir}/data |
...
Use the magnolia.content.bootstrap.pattern property , you can to specify which filenames will be imported and observed in the content bootstrap directory.
Example: magnolia.content.bootstrap.pattern=*/bootstrapDirdata/*.xml
Bootstrapping strategy
...
This task is configured in /modules/content-importer/tasks.
...
| heading | 0 |
|---|---|
| multiple | false |
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
Properties:
tasks | optional Tasks folder. |
| required Task name. |
| optional Users who can view and assign tasks.
|
| optional User groups who can view and assign tasks. |
| optional Message view displayed in detail view. |
| required
|
| optional Task title. |
Please note that at least one user or one group (see the next property) should be defined for bootstrap messages to be displayed. The default configuration comes with ...
The content message view is configured in /modules/content-importer/messageViews/content.
...
| heading | 0 |
|---|---|
| multiple | false |
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl p |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
| Mgnl n |
|---|
...
Properties:
messageViews | optional Message views folder. | ||||||||||||||||||
| required Message view name. | ||||||||||||||||||
| required Form definition node. Text fields (read only):
| ||||||||||||||||||
| required Actions definition node. | ||||||||||||||||||
| optional Configured actions:
| ||||||||||||||||||
| required Action bar definition. |
Overview
Content Tools