[MGNLDAM-566] Activation menus / actions should not be enabled if ancestors have not been published Created: 25/Mar/15 Updated: 01/Jul/15 Resolved: 07/May/15 |
|
| Status: | Closed |
| Project: | Magnolia DAM Module |
| Component/s: | DAM App |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.9 |
| Type: | Bug | Priority: | Major |
| Reporter: | Federico Grilli | Assignee: | AntonĂn Juran |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | usability, ux | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
The menus / actions for publishing an asset should not be enabled until all ancestors have been published. Otherwise this leads to confusing errors in the log like "Message received from subscriber: Parent content /restore/blabla/publications is not yet activated or you do not have write access to it. Please activate the parent content before activating children and ensure you have appropriate rights on blabla01" It's also the wrong behavior from a usability standpoint. |
| Comments |
| Comment by Richard Unger [ 26/Mar/15 ] |
|
+1 |