[LH4521] Invalid backup location produces no warning and no backup

Scrivener Windows Beta (Archived)
1

Per this recent thread.

Symptoms:
If your configured default backup path (or project-specific backup path) no longer exist, Scrivener does not alert you to the fact that you could not make a backup.

Reproduction:

  1. Create two test folders (e.g. C:\Test\DefaultBackup and C:\Test\ProjectBackup).
  2. Open a new test project.
  3. Set the Scrivener default backup location to the first test folder (e.g. C:\Test\DefaultBackup).
  4. Ensure that you are set to make a backup on manual save.
  5. Make an edit in your project and press Ctrl-S to save.
  6. Confirm that you see the new backup in your first test folder.
  7. Delete just the first test folder.
  8. Make another edit and press Ctrl-S to save.
  9. Note that the backup path is neither recreated nor is there a warning that your backup was saved. (If you have the console log on you will see warning that you could not create the ZIP file from a temp location, if you have the ZIP option selected, but this is still not a warning that the target path no longer exists.)
  10. Open the project settings and set your backup location to your second test folder (e.g. C:\Test\ProjectBackup).
  11. Make an edit in your project and press Ctrl-S to save.
  12. Confirm that you see the new backup in your second test folder.
  13. Delete just the second test folder.
  14. Make another edit and press Ctrl-S to save.
  15. Note that the backup path is neither recreated nor is there a warning that your backup was saved. (If you have the console log on you will see warning that you could not create the ZIP file from a temp location, if you have the ZIP option selected, but this is still not a warning that the target path no longer exists.)
  16. Reset your backup settings.

Ideally, Scrivener should warn you upon opening the project that you have an invalid backup path selected, and warn you again if something happens when trying to create a backup – giving you a chance to modify the location or fix the underlying problem and try again – before just continuing on. This is especially important for when you are closing Scrivener and would otherwise never now that you just failed to make a backup. If the backup location is on an external drive (or network path) that is no longer available, this could be really bad.

2

This is present in both 2.9.9.3 and 2.9.9.4, BTW – apologies for not including that info in the original post.

3

Given that when you first posted your article RC4 had not yet been released. I know cause I read it and RC3 still being listed. :slight_smile:

4

Thanks, devinganger! RC5 will add a warning message, if the backup location does not exist or is not writable.

5

Most excellent, tiho! Thanks for the prompt response.