Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
HTML Wrap
clearboth
width250
alignright
classmenu

Related topics:

...

The Tags app is a central place to where you manage content tags – keywords or terms assigned to a piece an item of content, see Content tagging. In AdminCentral, the app is accessible in the TOOLS group.

Info

The Tags This app manages content tags, which are different from the marketing tags. Marketing tags are advertizing – advertising or analytics code snippets that you insert on Web web pages . Marketing tags are managed using the Marketing Tags app.

...

The content-tags app is installed by the submodule magnolia-content-tags-ui.

The app stores nodes of the type mgnl:tag in the workspace tags.

Usage

Go to Tools > Tags to open the app. 

Tags app is installed by the Content Tags module and is based on the small app concept. The Tools app group that this the app belongs to is only available to the superuser role. This is configured in the app launcher layout. The app is configured at Configuration > /modules/content-tags .

Usage

 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 The Tahs app has two subapps:

  • The tag browser: Provides Tags browser – Provides a tree/list overview view of all the tags stored in the JCR repository and allows:'s tags workspace:
    Image Added
    In the browser, you can:
    • Add tags.
    • Rename tags.
    • Delete one or multiple tags.
    • Access the dependencies viewer that displays all the content items a tag is applied to (Show tagged content action).
    • Search

    • Adding new tags (the Add tag action in the Action bar).
    • Renaming tags (the Rename item action).
    • Deleting one or multiple tags (the Delete item action).
    • Accessing the the tag dependency view (via the Show tagged content action).
    • Searching for a tag or tags. 
      The search is case-insensitive, forward-matching looking and the its logic is applied to the node representation of the tag in the JCR repository's tags workspace (not to the actual name of a tag, but to its JCR node path. Thus, having defined the history and History tags, the following will occur:).
      This means that if, for example, you have both a history tag and a History tag, the following may occur when searching:


      Search string
      Search word
      Returned result(s)
      Name columnPath column
      history
      {t}

      Image Added history

      {t}

      Image Added History

      /h/hi/history
      /h/hi/History

      History
      {t}

      Image Added history

      {t}

      Image Added History

      /h/hi/history
      /h/hi/History
      hi
      {t}

      Image Added history

      {t}

      Image Added History

      {

      mgnl-f

      }

      hi

      /h/hi/history
      /h/hi/History
      /h/hi
      h

      Image Added history
      Image Added History

      Mgnl f
      h
      Mgnl f
      hi

      /h/hi
      <no results>
      /history
      /h/hi/History
      /h
      /h/hi
      /h
      {

      mgnl-f

      }

      h

      /h
      /hi<no results>*
      story<no results>

Image Removed

  • The dependencies viewer: Displays virtual URI mappings. Uses the boxes at the top of the table to filter by class, from URI or to URI.
    • * Because no path beginning with /hi was found.

  • Dependencies viewer – Shows which items are tagged with a particular tag across taggableWorkspaces (see Configure content dependency in the content-tags configuration). To open the viewer, doubleclick a tag in the browser or use the Show tagged content action.
    Image Added
    Each dependency listed is a clickable hyperlink that you can use to quickly open the tagged content item.

...