Why Are File Moves Not Propogating?

[eliyak]

I recently made some organizational changes (directory & file moves) on a synced network share, but I soon noticed that the changes are not being propagated to the remote sync. The log indicated no problems. I did a manual compare in the GUI, and the differences *were* detected, with an action of "Do Nothing." I can obviously fix this problem, but I want to know why it happened and if I can do anything to prevent it in the future when I may not be so vigilant.

The changes were made on the main share (Linux samba share), and FFS is running on a remote Windows 7 system where changes need to be propagated both ways. No changes were made to the remote files, so I would have expected FFS to at least detect that files were deleted and created elsewhere with no conflicts.

Any advice?

[eliyak]

FWIW, it turned out the problem was in the Time Span setting under Filter, which was at "This Month". This meant that any files that were moved (and therefore kept their old timestamp) were excluded from being synced.