-
Task
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
-
HL & LD 37, HL & LD 38
-
3
Current component/page creation flow:
- multi-step: first we select template/position which is not meant to be yet stored in JCR (we may cancel the action); we store this info in a transient bean and carry over to next step (properties dialog) and only then save everything to JCR.
- where do area nodes need to appear?
- currently parent node reference is already mixed in the transient bean at the component creation time (see the
PAGES-470re: why) - if we are talking about none existent area nodes, maybe we can defer the node creation to the very end.
- currently parent node reference is already mixed in the transient bean at the component creation time (see the
- depends upon
-
MGNLUI-6890 Make sure succession calls to JcrNodeWrapper #addNode and #getNode in the same session store info about path and node type
- Closed
- is depended upon by
-
MGNLFE-110 Handle missing area nodes in SPA
- Closed
-
MGNLFE-117 Create missing area nodes on client-side from template annotation endpoint
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...