-
Improvement
-
Resolution: Duplicate
-
Major
-
None
-
6.2.3
-
None
Situation:
The new 'jcr-browser-app' (coming with M6.2.3) uses 'config' as its default workspace, and not 'website' anymore.
Configured on the jcr-datasource.
Problem:
- Developers (front-end & back-end) using the JCR-Bowser are by far more interested in the 'website' workspace than in the 'config' workspace. Checking dialog saves etc.
- The 'Configuration' App already shows everything except the meta data... And checking the meta data in 'config' workspace is suuuper rare.
- Less and less configurations are in the config workspace, not much to check there.
Acceptance criteria
- duplicates
-
MGNLUI-6441 JCR app should default to website workspace
- Closed
- is related to
-
MGNLUI-6012 JCR Browser App: Please make workspace be a part of location fragment!
- Open
- relates to
-
MGNLUI-6489 JCR-Browser: Renaming of properties fails
- Closed