MNT-14671 enhancement allows sites to be deleted even when they contain at least one locked node (prior to that, the site deletion would be prevented). This was implemented by disabling the lockable aspect behaviour for site deletion.
I would expect the behaviour (sorry, no pun intended) to be symmetric when attempting to restore a site. Otherwise, you may see a stacktrace similar (but not identical) to:
- step1: write a JUnit test that demonstrates the issue and causes a similar failure to stacktrace above. In the absence of the thumbnail modification data (which shifted the issue, as per r129765) we may need to see if a custom behaviour onCreateNode policy can cause an update to the node, such that the restore site operation fails due to NodeLockException (on a read-only lock that is owned by someone other than the person doing the restore site, ie. site manager)
- DONE - see comment below => r133520 (DEV/5.2.N)
- step2: implement a fix that disables the lockable aspect behaviour when specifically restoring a site (in the same way that we do when deleting a site, see changes that were part of
MNT-14671). Enable the test.
- note to QA - peer review of the automated test, manual testing may not be required (other than re-running any existing tests around "restore site") unless we can identify suitable repeatable steps that cause the error (even after r129765)