Details
-
Sub-task
-
Status: Closed
-
High
-
Resolution: Fixed
-
None
-
None
-
None
Description
Currently, the browser perspective uses one model for both the selected folder (tree) and the selected document (listing). This makes it hard for plugins to find out what node they're supposed to use as their model. This imposes a significant burden on plugin developers that should be eliminated.
Attachments
Issue Links
- causes
-
CMS-1318 When plugins created on the fly, they do not get their correct model set through a ModelService
- Closed
-
CMS-1334 Foldertree: after creating a new document, focus in foldertree is lost and folder workflow steps disappear
- Closed
- includes
-
CMS-402 repository observation in frontend
- Closed
-
CMS-1431 Template editor: immediately update fields after changing parameter values
- Closed
- is a part of
-
CMS-1648 Implement observations
- Closed