-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 7.1
-
Fix Version/s: 5.6.0-HF43, 5.8.0-HF35, 6.0-HF17, 7.4
-
Component/s: Nuxeo Drive
-
Tags:
-
Sprint:Drive V2 EA feedback
Reproduced with Drive 1.4 against Nuxeo 7.1.
Steps to reproduce:
- sync a folder
- then sync a parent folder
=> the child folder should automatically be unsynchronized (so removed from the Nuxeo Drive folder)
- depends on
-
NXDRIVE-167 Relax constraint on factory name in FileSystemItem id to match 'deleted' or 'securityUpdated' events when updating remote states
- Resolved
-
NXP-11515 fileSystemItem attribute should not be None in the change summary entry for an unregistered sync root that can be adapted
- Resolved
-
NXP-14870 Drive: remote move to a folder registered as a sync root for another user is not handled as a local deletion
- Resolved
-
NXP-16038 Drive: deleting server-side a folder under a sync root for userA and registered as a sync root for userB won't delete the folder locally for userA
- Resolved
-
NXDRIVE-383 Enable back permission related tests
- Resolved
- is required by
-
NXDRIVE-385 Follow NXP-16478: fix drive root unsync when synchronizing parent root
- Resolved
-
NXP-17538 Drive: client might receive a 403 when trying to get a FileSystemItem for a non accessible doc
- Resolved
-
NXP-19439 Drive: remove fileSystemItemName from GetChangeSummary response when doc is not accessible
- Resolved
-
NXP-17541 Drive / GetChangeSummary: don't send a "deleted" event in case of a move to a synchronization root
- Resolved