I truly don't know whether this bug has been fixed since I haven't updated my program for a while.
Let's say I've synced something to a destination path of '\backups\%date%\A\'. Today, I'd get 'A' inside of '2022-01-10'.
If I were to sync to another 'B' folder in it (using '\backups\%date\B\') at the same day, instead of getting the same kind of result as above (an additional 'B' folder inside of '2022-01-10') as expected, the program would then re-create the date folder, and overwrite everything in it, as a part of the new sync. (I think it also ignored the '\B\' part and just placed everything inside the date folder - I'm not sure of this though, I can't try it now.)
The program does warn you about the huge difference between the source and target folders though (as usual).
Regards
Program Ignores Target Path Changes After Compare ?
- Posts: 5
- Joined: 5 Jan 2022
-
- Posts: 4056
- Joined: 11 Jun 2019
There is a missing '%' in your second example, not sure if that actually matter, but wanted to point it out just in case.
Are you running a "mirror" sync? Because you should be running update in the scenario you are describing. You can always run just the compare to preview what FFS will want to do and why.
Are you running a "mirror" sync? Because you should be running update in the scenario you are describing. You can always run just the compare to preview what FFS will want to do and why.
- Posts: 5
- Joined: 5 Jan 2022
Thanks for your advice (as well as for your comment to my other question).
I've tried to make it as suggested, but actually I just found out that the real problem is actually the program not recognizing the changes that I make to the Target path, as long as 'Compare' hasn't been performed.
My backup program runs with just 'backups\%date%\', to let me choose a different name for the new backup's folder. This way, the expected behavior when adding some folder name after this path ('\A')and pressing 'Synchronize', is that the program would sync into that inserted folder ('backups\%date%\A'). Instead, it doesn't recognize the change, and tries to sync into the initial path, i.e., 'backups\%date%\', which is wrong in my opinion. I could be wrong of course.
I changed the title to what it should now be.
I've tried to make it as suggested, but actually I just found out that the real problem is actually the program not recognizing the changes that I make to the Target path, as long as 'Compare' hasn't been performed.
My backup program runs with just 'backups\%date%\', to let me choose a different name for the new backup's folder. This way, the expected behavior when adding some folder name after this path ('\A')and pressing 'Synchronize', is that the program would sync into that inserted folder ('backups\%date%\A'). Instead, it doesn't recognize the change, and tries to sync into the initial path, i.e., 'backups\%date%\', which is wrong in my opinion. I could be wrong of course.
I changed the title to what it should now be.
-
- Posts: 4056
- Joined: 11 Jun 2019
I think i understand...
Can you attach and post the log file after running into this issue?
Also, if you run a compare, then make changes, then synchronize, FFS won't recognize those changes. This was a problem on another thread some time ago. Any changes made after running compare are only applied after running another compare.
Can you attach and post the log file after running into this issue?
Also, if you run a compare, then make changes, then synchronize, FFS won't recognize those changes. This was a problem on another thread some time ago. Any changes made after running compare are only applied after running another compare.
