Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
HTML Wrap | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Related topics: |
The Tags app is a central place to where you manage content tags – keywords or terms assigned to an item of content, see Content tagging.
Info |
---|
This app manages content tags, which are different from the marketing tags. Marketing tags – advertizing advertising or analytics code snippets that you insert on Web web pages – are managed using the Marketing Tags app. |
The app The content-tags
app is installed by the Content Tags Module and is configured at Configuration > /modules/submodule magnolia-content-tags
.
...
heading | 0 |
---|---|
enableHeadingAttributes | false |
enableSorting | false |
class | m5-configuration-tree |
enableHighlighting | false |
-ui
.
The app stores nodes of the type mgnl:tag
in the workspace tags
.
Go to Tools > Tags to open the app.
The Tools app group that the app belongs to is only available to the superuser
role. This is configured in the app launcher layout. Editors can only add and remove tags using the Add tags field in content app browser or detail subapps, once tagging is enabled.
The Tags app has two subapps:
...
Node name
...
Mgnl f |
---|
...
Mgnl f |
---|
In AdminCentral, the app can be launched from the Tools app group, which is accessible only to the users with the superuser
role. The Tags app is thus inaccessible to the editors since for them the main means of editing tags should be the tag fields in a content app's browser subapp or detail subapp, see How to enable content tags for a content app. In the case of Magnolia's Travel demo bundles this would be the Tours app.
The app has two subapps:
tags
workspace:Searching Search for a tag or tags.
The search is case-insensitive, forward-looking and its logic is applied not to the actual name node representation of a tag, but to its node representation the tag in the JCR repository's tags
workspace . Thus, having defined the history
and History
tags(not to the actual name of a tag).
This means that if, for example, you have both a history
tag and a History
tag, the following may occur when searching:
Search string | Returned result(s) | |||
---|---|---|---|---|
Name column | Path column | |||
history | |
| ||
History | | /h/hi/history /h/hi/History | ||
hi |
hi | /h/hi/history /h/hi/History /h/hi | ||
h |
h
hi | /h/hi/history /h/hi/History /h /h/hi | ||
/h |
h | /h | ||
/hi | <no results>* | |||
story | <no results> |
* Because no path that begins beginning with /hi
was found.
taggableWorkspaces
(see Configure content dependency in the content-tags configuration). To open the viewer, doubleclick a tag in the tag browser or choose use the Show tagged content action....