search

meganz / MEGAsync

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

v 5.2.0 : has no paths-exclusion! #916

Open LSmyrnaios opened 6 months ago

LSmyrnaios commented 6 months ago

Hi, I just did a "sudo apt full-upgrade" in Ubuntu 22.04 and the new version of Megasync was installed: "5.2.0-2.1"

When I logged in to MegaSync,I saw it downloading and uploading thousands of files that previously (up until version 4.12.2) I had excluded.

When I tried to exclude them again, I could not find that option in settings!

Please add back the exclusion-option.

salmanaligeek commented 6 months ago

Folders torn apart after upgrading :-( Seems like new version ate path exclusions.

cihe13375 commented 6 months ago

maybe because v5 introduces a new mechanism for exclusions (https://help.mega.io/installs-apps/desktop-syncing/exclusion-rules)?

LSmyrnaios commented 6 months ago

@cihe13375 thank you for the reference. I had no idea.

However, I shouldn't have to know it, anyway. The average user that used the same software for years and just updated the MEGAsync indirectly (not even explicitly). should not have to deal with the following issues:

1) Loosing all his exclusions and have his Mega account filled up with thousands of files that now has to delete manually from the cloud and local machines. This could take days or even weeks! >>> Mega-team please add a way to remove the exclusions from the cloud and local machines. <<< 2) Having to search for and read the documentation for how to use the new version that just came to him automatically. 3) The new exclusions menu is hidden and most users will never see it. Additionally to this, there should be a "Global exclusion list".

MEGA should have done the following: 1) Keep the the exclusions-list that each user had up until the 4.x versions and copy it to the new v.5.2.0. 2) Add some pop-up guide the first time the new version opens and teach the user about these kind of breaking changes.

rautamiekka commented 6 months ago

@cihe13375 thank you for the reference. I had no idea.

However, I shouldn't have to know it, anyway. The average user that used the same software for years and just updated the MEGAsync indirectly (not even explicitly). should not have to deal with the following issues:

  1. Loosing all his exclusions and have his Mega account filled up with thousands of files that now has to delete manually from the cloud and local machines. This could take days or even weeks! >>> Mega-team please add a way to remove the exclusions from the cloud and local machines. <<<
  2. Having to search for and read the documentation for how to use the new version that just came to him automatically.
  3. The new exclusions menu is hidden and most users will never see it. Additionally to this, there should be a "Global exclusion list".

MEGA should have done the following:

  1. Keep the the exclusions-list that each user had up until the 4.x versions and copy it to the new v.5.2.0.
  2. Add some pop-up guide the first time the new version opens and teach the user about these kind of breaking changes.

Amen to that.

redactedscribe commented 5 months ago

How was this allowed to happen?

Now I have 60,000 automatically uploaded files that were previously blacklisted over the years via the exclusions system prior to version 5. What am I supposed to do now? Why was no warning given to the user upon starting the new version? You spend over a year designing this new system and seemingly put no thought into the migration process. The minimum you could have done is to add a popup with pertinent information on how to migrate exclusions manually, and pause all transfers until the situation was understood. Is this incompetence, or a ploy to fill up my cloud drive and spam me with upgrade emails? The latter genuinely seems more likely. If it's incompetence, it brings into question the rest of your service...

Speak up MEGA.

Perkolator commented 4 months ago

3. Additionally to this, there should be a "Global exclusion list".

I was vocal about this (global exclusions in the client itself, not some dot file somewhere in the system) in the beta issue long time ago but they did not care.

Mega botched the version 5 launch. Nothing was done to inform the users about the big changes, nor to prevent obvious issues that would happen to some users.