FreeFileSync Forum

I'm still at v10.2 (after trying v10.11) because of the newly generated timestamped log filename (in stead of the needed fixed name LastSyncs.log).

Anybody an idea on how to persuade the author to combine best of both worlds ?

I've tried this - in the Override default log path - hoping to trick ...

Just tried v10.4 and once-again I've returned to v10.2.
It's nice to be able to change the logfile path (allthough I don't need it).
But the logfiles still have generated names (the name of the ffs-command-file followed by a timestamp).
In my scripts I just simply read the fixed-name "LastSyncs.log ...

(Copy/pasted my reaction here, from this thread .)
I went back to FreeFileSync_10.2_[Donation_Edition]_Setup.exe

After a few days of using 10.3 I noticed that my modified files did not appear at my Cloud Provider.
I soon found out that my own scripts work fine with 10.2 but not with 10.3. Due to ...

Thanks Plerry.
I'll copy my text to the other thread.

I went back to FreeFileSync_10.2_[Donation_Edition]_Setup.exe

After a few days of using 10.3 I noticed that my modified files did not appear at my Cloud Provider.
I soon found out that my own scripts work fine with 10.2 but not with 10.3. Due to the change "Deprecated batch-level log files and ...

I tried to send a complete dutch.lng to admin Zenju, but I can't find the mail-or-personal-message option...

So here it is. These are 2 existing lines:
<source>Updating file %x</source>
<target>File %x bijwerken</target>
Because everywhere in this lng file, the sourceword "File" is replaced with ...