-
Bug
-
Resolution: Fixed
-
Medium
-
5.5.3, 5.6.3, 5.6.4
-
None
A spinner and disabling of the button should be the bare minimum here to ensure the user knows that the move is in progress and cannot accidentally instigate the same page move again (which can lead to CONF-35040 - database deadlock).
For safety it should be enforced for an instance that while a page is currently being moved no other user (including users on another node) should be able to instigate a move of the same page.
Note that the root problem can probably be considered the fact that the page move operation is so slow (CONF-35396).
- is related to
-
CONFSERVER-35396 Page move action is too slow when moving a large number of pages
- Closed
- relates to
-
CONFSERVER-35040 Page move action causes database deadlock and data corruption
- Closed
-
CONFSERVER-34233 editor-loader overrides global $.ajax timeout
- Closed
-
CONFSERVER-35096 Error moving object with pages "JIRA Issue / Filter"
- Gathering Impact