search

meganz / MEGAsync

Easy automated syncing between your computers and your MEGA Cloud Drive
Other
1.59k stars 277 forks source link

Cannot exclude path with square brackets (invalid path) #713

Open redactedscribe opened 1 year ago

redactedscribe commented 1 year ago

As the title says, trying to add an exclusion for a path containing a square brackets isn't possible. MEGAsync complains with "Please enter a valid file name or absolute path".

Example path: D:\MEGAsync\BAK\Projects\[unnamed project]

Removing the closing bracket and pressing OK will allow the path to be accepted, indicating that the bracket is the issue. Interestingly, if instead you only remove the opening bracket, the path remains invalid.

The only way I've been able to make the exclusion be accepted (and I assume effective) is by adding an * before the opening bracket: D:\MEGAsync\BAK\Projects\*[unnamed project]. Of course, this is a broader exclusion than I need, but for my purposes, it should be working.

MEGAsync 4.6.8 64-bit Windows 11

dbm-mega commented 1 year ago

Hello. We've tested the issue and managed to reproduce the behavior you reported. It looks like folders starting with '[' are rejected when you try to add them to the exclusion list.

Our developers have been informed and are working on it. This will be fixed as soon as possible.

This kind of feedback is greatly appreciated - it helps improve our apps and makes MEGA a better platform.

redactedscribe commented 1 year ago

It looks like folders starting with '[' are rejected when you try to add them to the exclusion list.

As I noted: "if instead you only remove the opening bracket, the path remains invalid.", so it seems that a ] present is problematic too.

Our developers have been informed and are working on it. This will be fixed as soon as possible.

Thank you.

dbm-mega commented 1 year ago

Thank you for your comments. We have made sure that our developers have also this information.

mattw-mega commented 1 year ago

Hi @redactedscribe, we have an update coming up that fixes this, in fact it's a big change to how exclusions work, moving to a .megaignore file in the root of the sync. You can read about and perhaps help test it here: https://github.com/meganz/MEGAsync/issues/770 thanks