Hi Jason,

The syncing all depends on the "sync direction" you've set and how Windows treats items on disk and sets timestamps. Renaming folders is probably impossible to really solve as there is no way DMX can know about the old name. So the relation is lost. It then sees it as a new folder and the old one as having vanished. I can't see a workable solution for this frankly.

Peter

Yes, I see the issue here. Right now I have set up bi-directional syncing. However, the behavior seems to be that when a user renames or moves a folder, DMX deletes the files in the folder, creates a new empty folder with the new name leaving the user with two empty folders. Ideally the documents should not be deleted but should be now found in the renamed folder; or at least somewhere. A user just complained to me that she moved a folder and now all the documents are gone and this behavior was not expected.

I just did a test and I had a bi-directional sync folder with one document and one sub-folder. After these were added into DMX I moved the document into the sub-folder on the source (not from DMX). DMX saw that the original document was not where it was originally and deleted it from DMX which is fine, but then DMX sees the "new" document in the sub-folder of which there is no record of in DMX and deleted it as well. This is not desired behavior. It should have seen that the original document of which was in its database was no longer there and removed it as it did, but then seen the "new" document and imported it. If I do a copy first, then the "new" document gets put into the DMX database then I can delete the original, but when I do a move, all documents are deleted. I am going to have to turn off copy both ways for now as this is causing a loss of content. Please let me know if at least this behavior can be corrected (deleting "new" content that has been moved).

Hi Jason,

I'll make a note of it and see what I can do. We're revisiting Sync code for 5.3.4.

Peter

Hello, was the sync logic ever re-visited for 5.3.4? Just checking as I have not read through all the latest release notes. Thanks.

Yes it was as a matter of fact. And that was the last version it was touched to date (now on 5.3.7).

Peter

Hello, the behavior I noted back in 12/02/2010 still exists. Here is what I wrote back then:

I just did a test and I had a bi-directional sync folder with one document and one sub-folder. After these were added into DMX I moved the document into the sub-folder on the source (not from DMX). DMX saw that the original document was not where it was originally and deleted it from DMX which is fine, but then DMX sees the "new" document in the sub-folder of which there is no record of in DMX and deleted it as well. This is not desired behavior. It should have seen that the original document of which was in its database was no longer there and removed it as it did, but then seen the "new" document and imported it. If I do a copy first, then the "new" document gets put into the DMX database then I can delete the original, but when I do a move, all documents are deleted. I am going to have to turn off copy both ways for now as this is causing a loss of content. Please let me know if at least this behavior can be corrected (deleting "new" content that has been moved).

This is most likely due to the fact that the dates are not altered in Windows. The real issue is that there is no way for the software to tell the difference between a file that was there previously or one that was moved there recently. There is no watertight mechanism to determine if the file was there before or not AFAIK. I'll keep looking for a solution to this.

Peter