Inplace editing consolidation A: Bug-fixing
(MGNLUI-259)
|
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | content app, design |
| Affects Version/s: | 5.0 |
| Fix Version/s: | 5.0 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Mikaël Geljić | Assignee: | Mikaël Geljić |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Sprint: | Iteration 2013-17, Beta 2 | ||||||||
| Description |
|
Root node is selected when selecting JCR properties, this can be seen in the location change that sets the path token to /. Accordingly actions are then mapped to root node (add actions add items below root node, delete action is disabled). |
| Comments |
| Comment by Mikaël Geljić [ 03/Dec/12 ] |
|
traced it down to AbstractJcrContainer#containsId(Object itemId): AbstractJcrContainer.java @Override public boolean containsId(Object itemId) { if (itemId == null) { return false; } try { final Session jcrSession = MgnlContext.getJCRSession(getWorkspace()); return jcrSession.nodeExists((String) itemId); } catch (RepositoryException e) { throw new RuntimeRepositoryException(e); } } This obviously exludes properties when Table handles selection and checks if data container contains an Item with such path. |
| Comment by Mikaël Geljić [ 03/Dec/12 ] |
|
by the way, selecting paths for properties such as mgnl:created or anything:something will turn location controller crazy and won't be able to refresh page. Should probably file another ticket for escaping location fragments. |