Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
...
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 a tag or tags.
The search is case-insensitive, forward-looking and its logic is applied not to the actual name of a tag, but to its node representation in the JCR repository's tags
workspace. Thus, having defined the history
and History
tags, the following may occur:
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> |
* Zero results even in the Path column because no path begins with /hi
.
...