[MGNLTAGS-75] Migrate to new workspace (5.6.x)/ prevent installation alongside Content Tags Module (5.5.x) Created: 21/Jun/17  Updated: 10/Oct/17  Resolved: 07/Jul/17

Status: Closed
Project: Marketing Tags Manager
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3

Type: Task Priority: Neutral
Reporter: Antti Hietala Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones CONTTAGS-3 Use the existing tags workspace Closed
causality
is causing MGNLDEMO-218 Marketing tags were migrated to new w... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Date of First Response:
Epic Link: Tagging
Sprint: Kromeriz 101, Kromeriz 103, Kromeriz 104
Story Points: 2

 Description   

The tags workspace and tag node type are currently used by the Marketing Tags module. You will have a conflict until we can resolve it in the next major release.

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

Generated at Mon Feb 12 10:14:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.