MEGAsync
MEGAsync copied to clipboard
Override cloud files with local ones
I had a following scenario:
- The synchronization was off
- I removed a folder locally
- Turned on the synchronization
- 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.
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
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.
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.
In that case you want to EXIT/QUIT MEGAsync:
- If you delete data from the local/remote synced folder, when you open it again, MEGAsync will reflect the changes and delete the corresponding data in the remote/local sync folder.
- If you move data from the local/remote synced folder into a local/remote synced subfolder, when you open it again, MEGAsync will reflect the changes in the remote/local sync folder.
Please let us know if this solves your concern.
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