diff options
| author |  openmedi <openmedi@web> | 2016-05-12 06:52:51 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2016-05-12 06:52:51 +0000 |
| commit | 11deb360dfbdeb68316c6f91fe627fed714e5307 (patch) | |
| tree | 586cbf7b29d35a651a1fe90a8999aa0bdbb6675d | |
| parent | 6d8d14d8d0f92e66ef3dceea9d4b1a59325bb484 (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/Deleting_remotes_doesn__39__t_work__8230__/comment_1_01d244f44d439ad08681af88284103c8._comment | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/forum/Deleting_remotes_doesn__39__t_work__8230__/comment_1_01d244f44d439ad08681af88284103c8._comment b/doc/forum/Deleting_remotes_doesn__39__t_work__8230__/comment_1_01d244f44d439ad08681af88284103c8._comment new file mode 100644 index 000000000..3e1f171bd --- /dev/null +++ b/doc/forum/Deleting_remotes_doesn__39__t_work__8230__/comment_1_01d244f44d439ad08681af88284103c8._comment @@ -0,0 +1,7 @@ +[[!comment format=mdwn + username="openmedi" + subject="comment 1" + date="2016-05-12T06:52:50Z" + content=""" +This didn't work, because syncing was disabled before trying to delete the remote. Deleting involves putting the remote in the unwanted group and through active syncing remove all the content from it, before deleting it fully. The assistant should be able to handle starting deletion processes, even when synching is disabled. At least there should be a dialogue telling the user that synching is disabled and therefore the deletion process will not start. +"""]] |