Details
-
Bug
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
CE-test-webapp, build 6.2
Snapshot: 2019.11.03 12:21:32
-
-
Empty show more show less
-
UI Framework 14
-
2
Description
New description
The actions available for a node marked for deletion should should be the very same as we have it on the old version of the dam app. These are:
- Publish deletion
- Restore previous version
Other actions are not required.
Â
Â
Â
Initial context:Â Deleting assets which were never public may throw an exception
With the new version of the Assets app the action Publish Deletion has been removed.
Instead one can now use
- PublishÂ
- Publish incl. subnodes
to finally get rid of nodes marked for deletion.
Both actions will finally, completely delete the node(s) on the author context.
But:
When using the latter ( Publish incl. subnodes) and if the nodes which are "marked for deletion", never had ben published, then, executing the action Publish incl. subnodes will throw an exception.
stack-traceerror
Again:
The deletion of the nodes works fine, and that was what the user wanted to achieve.
But the exception - also noted with a red "error banner" - most probably will confuse the user.
Possible solution:
Since I can delete both a single node or a node with all its subnodes - when executing Publish on such node with children (where th eparent and the subs are marked for deletion) ...
... we probably could ... no we should disable most of the actions - if the selected node is marked for deletion.Â
"Real" context: Limit available actions for nodes marked for deletion
As written above, limiting the context of available actions when the selected node is "marked for deletion" is a must.
Much too much "nonsense" options available.
Â