The default rules had absolute destinations hardcoded to the Downloads folder (e.g. C:\Users\...\Downloads\Images). This caused files from any watched folder to always be moved to Downloads instead of being sorted locally.
Changes:
Default rules now use relative destinations (Images, Documents, Archives...)
execute_rule resolves relative destinations against the source folder where the file appeared
Added automatic database migration on startup: existing absolute rule paths are converted to relative on first launch
Files dropped into C:\TEST with the "Images" rule now correctly go to C:\TEST\Images
Originally posted by: hsr88
Fixed in [#7]dfe22b.
The default rules had absolute destinations hardcoded to the Downloads folder (e.g.
C:\Users\...\Downloads\Images). This caused files from any watched folder to always be moved to Downloads instead of being sorted locally.Changes:
Images,Documents,Archives...)execute_ruleresolves relative destinations against the source folder where the file appearedC:\TESTwith the "Images" rule now correctly go toC:\TEST\ImagesThanks for the report!
Related
Tickets:
#7Ticket changed by: hsr88