Did you just edit one field?
Can you add a few extra rows and try?

Sync doesn't sync files if the file size remains the same, so maybe that optimization is kicking in here.

Very quick testing shows it takes .5kb to cause a sync.

ok, just to confirm, was your previous edit just editing one row?

Initially my edit was a typical one for the function of the file, pretty tiny, just a handful of characters.

In order to get a sync I had to add data to to multiple rows.

I would think somewhere there is documentation regarding what specifically triggers a sync? Then we wouldn't need to be going back and forth like this

While I used to write software and fretted the details, now I'm a pretty simple guy, so I would expect the time stamp should do the trick.

Unfortunately, Tonido Sync only uses File Size to trigger changes. I think it ran into a problem when the size wasn't changed but the file was.

We will look into this and see if we can add other checks.

Is this still an issue in the current version of Sync? I suspect I'm running into this issue where the file has changed on the client but the size is the same and even though the log indicates it recognized the file system change, the modified file is never updated on the server. Can't you use something like an MD5 checksum to detect file content changes?

We don't do md5 checksum all the time, we use modified date and file size to trigger changes. Using md5 checksum would be very cpu intensive. We do use md5 sum at other points in the sync process.

I see. Well I confirmed this is still happening by making changes that would trigger the file size change - as apposed to a simple spelling correction - and the update was kicked off almost immediately.

I must say that this is a pretty big limitation over something like dropbox. I only noticed it after recalling that I had updated several files on a client system which the size didn't change but the timestamp was different, yet the updated file was never uploaded to the server. The date/time was about a week apart between the client system and the plug.

Are you sure the file modified wasn't being changed as well?
We do check against that as well so even if size doesn't change, the modified should handle it.

Could you clarify that question? Are you asking if the timestamp of the file I'm modifying is changing? The date/time is definitely changing, in fact the contents are changing too. For example, I run spell check to fix some spelling errors then save and close the file. The size might not change (at least when rounded to KBs) but the contents of the file definitely change even if slightly. However I see in the log that a 'FS change detected' event gets logged (10 times in a row) but I never see the upload event.

I re-open the same file an hr later and change an entire paragraph or drop in an image, save, close - file gets uploaded to plug less than 15 seconds later.