Uploaded image for project: 'XWiki Platform'
  1. XWiki Platform
  2. XWIKI-20811

Page lock warning when resolving a version conflict by selecting "Reload the editor (discard changes)"

    XMLWordPrintable

Details

    • Bug
    • Resolution: Invalid
    • Blocker
    • None
    • 14.10.6
    • Edit
    • Windows 11 Pro, Edge 111, using a local instance of XWiki 14.10.7 on MariaDB 10.11, Tomcat 9.0.73, reproducible also on Jetty/HSQLDB
    • Unknown

    Description

      Steps to reproduce

      1. Login as Admin
      2. Go to a page
      3. Open the same page in a different browser (or an incognito window) and login with the user (U1) there
      4. With Admin, edit the page in-place (insert e.g. 'edit1')
      5. Click 'Save'
      6. With U1, on the incognito window (force edit the page if the case), add some text e.g. 'edit2' on the same line
      7. Click 'Save'
      8. Go back to the browser where Admin is logged in and type a word (e.g. 'edit3') in the same line
      9. Click 'Save'
      10. On the Version Conflict box, select 'Reload the editor (Discard changes)'
      11. Click 'Save'

      Expected results

      The page lock is not displayed and the content is saved with the last modification saved by the user (e.g. 'edit2').

      Actual results

      A page lock is displayed that the page is currently locked by U1. However, the content is saved as expected.

      The lock could be reproduced also on XWiki 14.10.6 and 14.10.7, but could not be reproduced on XWiki 14.10.5.

      Attachments

        1. Editing_conflict_Reload.png
          76 kB
          Ilie Andriuta
        2. Lock_Reload_Editor.png
          39 kB
          Ilie Andriuta

        Issue Links

          Activity

            People

              mflorea Marius Dumitru Florea
              iandriuta Ilie Andriuta
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: