[MGNLDATA-120] ActivateAll and DeactivateAll commands not using workflow Created: 03/May/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 1.6.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Matt Dertinger Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 1
Labels: activation, configuration, workflow
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Hi,

Currently the data modules activateAll and deactivateAll commands to not use the activation and deactivation workflows. I believe the behavior of these commands should be similar to the activate and deactivate commands which are configured to use the workflows.

Note: The deleteAll command may also be impacted, since it calls to the deactivateAll command.

Please let me know if you have any questions.

Cheers,
Matt



 Comments   
Comment by Philipp Bärfuss [ 04/May/11 ]

Somehow I am in favor of removing this by default. The command could still be present and a tool page with some big read warning messages could allow their execution.

WDYT?

Comment by Matt Dertinger [ 04/May/11 ]

Philipp,

I think that would be a good option. Would the deleteAll command also be moved to the Tools area?

Cheers,
Matt

Comment by Philipp Bärfuss [ 05/May/11 ]

Yes, or a new menu entry in the "Data" menu section.

Comment by Jean-Francois Nadeau [ 06/Jun/12 ]

There is 2 options that would help us.
1 - Add the workflows to the activateAll and deactivateAll buttons.
OR
2 - Have an option to only show the buttons to publishers.

thanks

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 05:11:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.