[MGNLDAM-948] Subfolders of Unpublished Parent Folders Should Not Be Allowed To Be Published Created: 24/Feb/20  Updated: 18/Nov/21  Resolved: 03/Nov/21

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: 3.0.5
Fix Version/s: 3.0.11

Type: Bug Priority: Neutral
Reporter: Julian Nodarse Assignee: Nguyen Phung Chi
Resolution: Fixed Votes: 0
Labels: cm-team-support, maintenance
Remaining Estimate: Not Specified
Time Spent: 2d 6.5h
Original Estimate: Not Specified

Attachments: PNG File Error.PNG     PNG File Fixed in 6.2.png     PNG File Stories Folder Example.PNG    
Issue Links:
Problem/Incident
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Release notes required:
Yes
Date of First Response:
Sprint: Assets Maintenance 1
Story Points: 2

 Description   

An error pops up when publishing child folders whose parent folders are not published. It makes sense for the error to show up, since the parent isn’t published. However, users should not have the option to publish these child folders without the parent being published first.

This can be reproduced on the demo.

You can use the stories app as an example: Create a folder and two more sub folders as seen on the screenshot. Try to publish the child node without publishing the parent node. You will receive a “publication failed” error. 

Expected result:

  • Publish and Publish include subnodes actions should be available when its parent is published in Assets app

Notes:

  • Found out another issue while working on this, the Unpublish action available even when the folder/asset is unpublished.
    • Adding an availability rule for this case also

 



 Comments   
Comment by Simon Lutz [ 13/May/20 ]

Fixed in 6.2:

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