I am using 64-bit FreeFileSync 3.7 on Windows 7 to maintain our backup and
restore files, but when I run the _batch file I have generated in that 3.7
version on a system running 3.6, I get an error that it could not read the XML
node <Active>, which I think is the flag to activate the filter.
In 3.7, when I look at the Filter tab in the bottom left of the main window, I
only see an option to show excluded files, I do NOT see an option to
"Activate Filter".
Is that flag supposed to be there in 3.7 or just missing in the 64-bit
version? Do I need to do something to show that control element? Screenshots
can be provided if necessary.
Could not read XML node <Active>
- Posts: 74
- Joined: 17 Mar 2008
-
- Site Admin
- Posts: 7064
- Joined: 9 Dec 2007
This is a migration issue, see [404, Invalid URL: https://sourceforge.net/tracker/?func=detail&aid=3006259&group_id=234430&atid=1093080]
The solution is to migrate old configuration files manually (just open them
with the new version and overwrite them)
The solution is to migrate old configuration files manually (just open them
with the new version and overwrite them)
- Posts: 74
- Joined: 17 Mar 2008
I have done just that, opened our old files in the new 3.7, made some minor
edits, saved them wtih the same name, and 3.6 throws an exception, so what I
had to do was just use 3.6 to edit them, because we are still running 3.6 as
our standard version. I could also just migrate to 3.7 across the board, we
are still in testing phase so that's easy, but where do you store the change
log or the release notes for each new version?
edits, saved them wtih the same name, and 3.6 throws an exception, so what I
had to do was just use 3.6 to edit them, because we are still running 3.6 as
our standard version. I could also just migrate to 3.7 across the board, we
are still in testing phase so that's easy, but where do you store the change
log or the release notes for each new version?
-
- Site Admin
- Posts: 7064
- Joined: 9 Dec 2007
> but where do you store the change log
The changelog comes bundled with each release in a aptly named file
"changelog.txt".
> 3.6 throws an exception
v3.7 introduced a configuration change that added one xml node and removed
another. This combination unfortunately makes the config files neither upwards
nor downwards compatible. In general I expect and try to keep configuration
stable, but this time.. oh well
The changelog comes bundled with each release in a aptly named file
"changelog.txt".
> 3.6 throws an exception
v3.7 introduced a configuration change that added one xml node and removed
another. This combination unfortunately makes the config files neither upwards
nor downwards compatible. In general I expect and try to keep configuration
stable, but this time.. oh well
- Posts: 74
- Joined: 17 Mar 2008
Ok, sarcasm duly noted (grin)...I'll have a read over the changelog!
Totally understand about the xml, our situation is easily remedied by simply
migrating entirely to 3.7, which we will do, thanks again for all your help!
Totally understand about the xml, our situation is easily remedied by simply
migrating entirely to 3.7, which we will do, thanks again for all your help!
