[MGNLUI-1541] Path in location should be relative to workbench root Created: 04/Jun/13  Updated: 02/Jul/13  Resolved: 02/Jul/13

Status: Closed
Project: Magnolia UI
Component/s: framework, security app
Affects Version/s: 5.0
Fix Version/s: 5.0.1

Type: Bug Priority: Critical
Reporter: Tobias Mattsson Assignee: Jozef Chocholacek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-1562 Browser with path set in workbench ge... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

In the Security app the sub apps for users show the contents of /admin and /system respectively. The path in the location however should not include these.

In SecurityApp.start the sub apps are started with these paths in the location. This should be changed to "/".

In BrowserSubApp the location needs to be updated setting the path as relative to the workbench root.

In BrowserSubApp when the location changes it needs to find the item to select relative to the workbench root.



 Comments   
Comment by Eric Hechinger [ 02/Jul/13 ]

No need to change the BrowserPresenter and expose a getWorkbench() as it is already available :
subAppDescriptor.getWorkbench().getPath();

In addition :
Not sure of the logic changed there:

String newPath = subAppDescriptor.getWorkbench().getPath();
itemId = JcrItemUtil.getItemId(SessionUtil.getNode(workspaceName, newPath));
>> Item is retrieve from the configure path ("tutu")
BrowserLocation newLocation = getCurrentLocation();
newLocation.updateNodePath("/");
>> but location is always set to "/"

Generated at Mon Feb 12 08:47:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.