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.
- Publish and Publish include subnodes actions should be available when its parent is published in Assets app
- 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