Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 11.2
-
Component/s: Old Core
-
Labels:None
-
Difficulty:Unknown
-
Documentation in Release Notes:
-
Similar issues:
Description
The conflict mechanism has been introduced in XWIKI-6665 and might have introduced some unwanted behaviours on custom extensions due to the need of keeping up-to-date the version of the document being edited when saving an object.
This problem is certainly mitigated by XWIKI-175 solution, but we don't have enough feedback right now to be sure.
In order to bulletproof a bit our solution, it would be better to have a switch off property for the conflict detection, to be able to work around any unexpected issue.
Attachments
Issue Links
- relates to
-
XWIKI-6665 Saving edits after lock expiration doesn't warn the user that the page may be stale
-
- Closed
-
-
XWIKI-175 Merge on Save
-
- Closed
-