-
Bug
-
Resolution: Fixed
-
Major
-
5.3
-
-
Empty show more show less
-
5.3 Sprint 4, 5.3 Sprint 5, 5.3 Sprint 6
CreateItemAction hasn't been liberated from JCR just yet, so it is not aware of ContentConnector and therefore appends a JCR absolute path to the DetailLocation.
This was causing troubles to the data module where rootPath of both browser and detail subApps is not the absolute root of the 'data' workspace (e.g. /companies, see cloned issue).
Using ContentConnector#getItemUrlFragment should account for that just fine.
Acceptance criteria
- clones
-
MGNLDATA-252 Adjust bootstraps & MVH for migration to jcr-agnosticism
- Closed