-
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"
-
- Closed
-
[CONFSERVER-34870] The page move UI should provide feedback when the move is slow and multiple concurrent moves of the same page should be prevented
Workflow | Original: JAC Bug Workflow v3 [ 2888273 ] | New: CONFSERVER Bug Workflow v4 [ 2981873 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2797720 ] | New: JAC Bug Workflow v3 [ 2888273 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Bug Workflow [ 2727859 ] | New: JAC Bug Workflow v2 [ 2797720 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2392689 ] | New: JAC Bug Workflow [ 2727859 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2288523 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2392689 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2227299 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2288523 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2182732 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2227299 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1950924 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2182732 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v3 [ 1744633 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 1950924 ] |
I agree. We have this issue in our system as well with large copy's or moves. Can we get some kind of indicator to the end-user about the process running.