[magnolia-dev] [JIRA] (MGNLTAGS-75) Migrate to new workspace

Roman Kovařík updated an issue

Marketing Tags Manager / https://jira.magnolia-cms.com/browse/MGNLTAGS-75 MGNLTAGS-75

Migrate to new workspace

Change By:
Roman Kovařík

Persist content tags in the {{tags}} workspace. Store them hierarchically as the number of nodes in the workspace can grow rapidly impacting performance of the Tag Management app. See [Technical prerequisites, recommendations|https://wiki.magnolia-cms.com/display/PMTEAM/Tagging+content#Taggingcontent-Technicalprerequisites,recommendations]

Use the {{mgnl:tag}} node type.

(!) The tags workspace and tag node type are currently used by the [Marketing Tags module|https://documentation.magnolia-cms.com/display/DOCS/Marketing+Tags+module]. You will have a conflict until we can resolve it in the next major release.
* Warn users about the conflict. It should not be possible to use the Tags module and the Marketing Tags module simultaneously.
* Add a conditional install task that prevents the user from installing both modules on the same instance.
* Don't bundle the new Tags module with Magnolia.

In the next major release (Magnolia CORE 5.6):
* Increment the major version of Marketing Tags.
* Migrate marketing tags out of the {{tags}} workspace into a new {{marketing-tags}} workspace.
* Create a new content type {{mgnl:marketing-tag}}
* Start using the {{tags}} workspace for content tags.
* Start using the {{mgnl:tag}} content type for content tags

https://jira.magnolia-cms.com/browse/MGNLTAGS-75#add-comment
Add Comment

This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)

----------

----------------------------------------------------------------

For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html

Alternatively, use our forums: http://forum.magnolia-cms.com/

To unsubscribe, E-mail to: <[email protected]>

----------------------------------------------------------------