Uploaded image for project: 'Hippo Site Toolkit 2'
  1. Hippo Site Toolkit 2
  2. HSTTWO-3520

When a component item gets moved from one container to another, make sure that both containers get directly locked

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Top
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.0
    • Component/s: None
    • Similar issues:

      Description

      Since a move between two containers involve two separate update calls from the frontend, normally, both containers get locked : However, during the first call, only the 'target' container gets locked, and during the second call, the 'source' container gets locked.
      Since however the fix in HSTTWO-3314, the second update can now fail because the source container already during the first call gets it 'last modified timestamp' updated. As a result, the frontend does the second call with a timestamp that is not in sync any more, and thus an error is returned. For example

      {"success":false,"message":"Node '/hst:hst/hst:configurations/hap-preview/hst:workspace/hst:containers/base/footer' has been modified wrt versionStamp. Cannot acquire lock now for user 'admin'.","errorCode":null,"data":[]}
      

      As a result, the 'source' container never gets locked. The frontend also shows an error popup that the page gets reloaded. After this, all seems to be fine again. However, if the editor 'discards' his changes, the moved container item is gone from both the target and the source container

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                pgupta Pankaj Gupta (Inactive)
                Reporter:
                aschrijvers Ard Schrijvers
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: