[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, |
| 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, |
| 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. 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. |