Details
-
Bug
-
Resolution: Unresolved
-
Neutral
-
2.0.2
-
None
Description
At the current moment, locking a node locks renaming node children as well. This can be confusing for the client, since the lock only affects the parent node.
For this reason, it would be a good idea to disable the rename action on children nodes to avoid confusion.
Reproduce
Actual
Lock exception thrown:
ERROR info.magnolia.ui.contentapp.browser.ActionExecutionService 23.05.2023 09:43:49 -- An error occurred while executing action [commit] info.magnolia.ui.api.action.ActionExecutionException: Action execution failed for action: commit at info.magnolia.ui.api.action.AbstractActionExecutor.execute(AbstractActionExecutor.java:64) ~[magnolia-ui-api-6.2.33.jar:?] at info.magnolia.ui.contentapp.browser.ActionExecutionService.executeAction(ActionExecutionService.java:70) ~[magnolia-ui-framework-6.2.33.jar:?] at info.magnolia.ui.framework.action.service.CompatibilityActionExecutionService.executeAction(CompatibilityActionExecutionService.java:129) ~[magnolia-ui-framework-compatibility-6.2.33.jar:?] ... ... ... Caused by: javax.jcr.lock.LockException: Node locked. at org.apache.jackrabbit.core.lock.LockManagerImpl.checkLock(LockManagerImpl.java:694) ~[jackrabbit-core-2.20.9.jar:2.20.9] at org.apache.jackrabbit.core.lock.LockManagerImpl.checkLock(LockManagerImpl.java:670) ~[jackrabbit-core-2.20.9.jar:2.20.9] at org.apache.jackrabbit.core.lock.LockManagerImpl.checkLock(LockManagerImpl.java:655) ~[jackrabbit-core-2.20.9.jar:2.20.9] at org.apache.jackrabbit.core.lock.XALockManager.checkLock(XALockManager.java:174)
Expected
Rename action should be disabled in the UI.
Checklists
Acceptance criteria