meganz / MEGAsync

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

Override cloud files with local ones #697

Open Pramuspl opened 2 years ago

Pramuspl commented 2 years ago

I had a following scenario:

  1. The synchronization was off
  2. I removed a folder locally
  3. Turned on the synchronization
  4. The removed folder has been synced back from the cloud to local

I didn't manage to find a way to prioritize local files over the cloud ones when syncing.

aunetx commented 2 years ago

This happens for me too, for a bunch of pdf files -- I think I managed to remove this by removing them from mega cloud drive and my computer at the same time, but that's not very practical

angelds-mega commented 2 years ago

Hello.

If you delete something while the synchronisation is inactive, the deletion will not be detected.

When the synchronisation starts, all missing files on either side will be transferred from the other side.

This is expected behaviour.

If you want a deletion to be replicated to the other side, you have to perform it while the synchronisation is active.

Pramuspl commented 2 years ago

Hello.

If you delete something while the synchronisation is inactive, the deletion will not be detected.

When the synchronisation starts, all missing files on either side will be transferred from the other side.

This is expected behaviour.

If you want a deletion to be replicated to the other side, you have to perform it while the synchronisation is active.

That's my point. Let's say I'm somewhere with no Internet access. I want to spend that time tidying my cloud so I start removing items locally - once I reconnect they'll be downloaded again.

I strongly believe there should be a possibility to 'force push' the state of the cloud.

voc-mega commented 2 years ago

In that case you want to EXIT/QUIT MEGAsync:

Please let us know if this solves your concern.

mattw-mega commented 1 year ago

Hi @voc-mega , @Pramuspl @angelds-mega @aunetx, you will hopefully be pleased to know we have a big update coming up which will address this issue in MEGASync. Instead of "off" (disabled state) we now have Suspended state which is the default and which will behave as you expect. You can read about it and perhaps help test it here: https://github.com/meganz/MEGAsync/issues/770 thanks