I had to update Hazel to version 5.2.2 from 5.1.1 to find the "Replace Folder" command.
Is this the same as the command in the Hazel guide located here:
https://www.noodlesoft.com/manual/hazel/attributes-actions/action-reference/relocating-folders/ ? It seemed like a different command as it uses the word "relocate" instead of "replace".
This bulk replace folder is going to save me days of work! Thank you so much.
Testing phaseI want to be sure that this will work in the way intended so I have been experimenting with throw-away folders and files. It seems like a very delicate thing to fiddle with. But after a few hours of testing I can see it is likely to work.
Initially I thought it only did half the job in my situation..... until I found a work-around
This is what worksIf I have a file destination /myfiles/
boxcryptor/onedrive/scans, I can change every rule using that final destination "scans" to a new destination: /myfiles/
cryptomator/onedrive/scans.
In order for this to work I must have at least one rule which moves, copies, or synchs a file to /myfiles/
boxcryptor/onedrive/scans
That's great so far, as I have hundred's of rules referencing that folder called "scans". So that's half the job done.
This what seemed to be the problemHowever I also have hundreds of rules referencing unique folders, e.g.
/myfiles/
boxcryptor/onedrive/bank statements
/myfiles/
boxcryptor/onedrive/doctor bills
/myfiles/
boxcryptor/onedrive/shopping invoices
/myfiles/
boxcryptor/onedrive/investments
/myfiles/
boxcryptor/onedrive/utilities bills
It would take forever to change each one of these unique destinations using the aboive method.
In every case I needed to replace the "boxcryptor" destination by the "cryptomator" destination. However under the "Replace" command there was no folder for "boxcryptor" showing on the left hand side.
The work-aroundI resolved it by creating a new rule which moved a file to "Boxcryptor". Then when I click on Hazel menu bar, Folder, Replace Folder, it shows "Boxcryptor" in the list of existing destinations on the left hand side, and I then instruct it to replace it with "cryptomator".
The path remains intact with merely the word "boxcryptor" replaced by "cryptomator" in every file path in every rule.
What remains to be doneFor the rule to work properly, I'll need to re-create the entire folder structure underneath "cryptomator" in exactly the same way as it was under "Boxcryptor". That's literally hundreds and hundreds of sub-folders. I think there is a function in Hazel to do that, but I have not investigated it yet.
I'll let you know when the job is done successfully.
By the way, thanks very much for the prompt reply. I appreciate that after all these years you still monitor and respond in the forums!