Commands refactoring (MAGNOLIA-4782)

[MAGNOLIA-4785] Move the commands definitions in website and dms catalog to Pages and DAM app modules Created: 21/Jan/13  Updated: 11/Feb/13  Resolved: 30/Jan/13

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0

Type: Sub-task Priority: Neutral
Reporter: Jozef Chocholacek Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-567 Implement direct content activation Closed
is related to MGNLDAM-96 Move the commands definitions in dms... Closed
Template:
Release notes required:
Yes
Date of First Response:

 Description   

Move the activate and delete command definitions in the website and dms catalogs to the Pages App and DAM App modules, as described in http://wiki.magnolia-cms.com/display/DEV/Concept+-+Commands

Update the version handles of those modules to assure that they will remove the old definitions on upgrade (and create the new ones if needed).



 Comments   
Comment by Daniel Lipp [ 30/Jan/13 ]

There should be commits to magnolia_main, magnolia_ui & modules/dam so we'd need three tickets (at least) that are somehow linked.

Comment by Eric Hechinger [ 01/Feb/13 ]

As pages is in UI, we only have two related tickets.

Generated at Mon Feb 12 03:59:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.