Save Error, failed to auto-save file /path/to/file

[Deniero]

Currently, saving a new Entry is not possible, as I get an error message: Save Error, failed to auto-save file /path/to/file
I could not find an error in the logs.
I am using Nextcloud 21, before upgrading, I did not had this problem. However I have no idea if the problem is due to the upgrade.
I would be grateful, if someone has a possible solution.
Thanks

[arnowelzel]

Can you please check the JavaScript console of your browser if there is a more detailed error?

[ggwashburn]

I am having the same issue. Nextcloud version: 20.0.8 - 20.0.8.1. When I make any change to an entry or add an entry, it seems to save. But when I navigate away from the Keeweb page to another page on the site such as Files, I get an error popup that says "Leave Site? Changes you made may not be saved." And in fact they are not saved when I navigate back to the Keeweb page to view my KeePass database again. I checked the Javascript console and other than deprecation warnings there is an error when I go to the Keeweb page when it displays the form requesting password for you keepass file.

excludeClickOutsideClasses.js:22 Uncaught TypeError: Cannot read property 'contains' of undefined
at a.hasNodeOrAnyParentClass (excludeClickOutsideClasses.js:22)
at a.clickOutsideMiddleware (excludeClickOutsideClasses.js:22)
at r (v-click-outside.umd.js:1)
at v-click-outside.umd.js:1

[arnowelzel]

I'm sorry, but I can't reproduce this problem. Keeweb works fine here in Nextcloud 20 and 21 without any issues.

[arnowelzel]

Can you tell me the exact browser name and version and which operating system you use? Also if you use any plugins.

[tobiaseigen]

I am experiencing the same issue as @ggwashburn today, just doing a test of keeweb for the first time. It is a slick app and hope I can move to it. Nice work!

I'm on NC21 stable branch, use chrome on OSX. I have duck duck go plugin. I just checked with safari on osx and had the same issue. It appears to save, but then when I click away I get the warning I will lose my changes. Let me know if there is anything else I can do to help troubleshoot this issue.

[arnowelzel]

Can you try using another browser just to see if it is a browser issue? Thanks.

[tobiaseigen]

I'm unable to save in chrome, safari on osx. Also unable to save in safari on ios.

I will take a look at my server logs and see if anything obvious jumps out at me.

this is a site I recently upgraded to NC21 from a very old version.. so maybe there is some other problem? I also am having difficulty running occ on my server from the CLI, but that is probably unrelated to this problem. Otherwise NC seems to be going strong without issue.

Thanks!

[tobiaseigen]

ok I have now figured this out. The error message is unfortunate and buggy looking, and maybe can be improved. But it's actually expected behavior. You want to save changes by closing the file before leaving the tab on the menu. The way to save changes manually is by selecting the LOCK button in the bottom right (looks like an exit to the right arrow).

In the options, I also was able to set it to automatically save and sync every minute. Since then I have not seen this error at all!

I was only able to figure all this out by thinking like I'm in 1pass, which has a similar UI. All the essential functions are hidden behind cryptic looking icons along the bottom. This is nice once you know how it works but until you figure it out it is a little frustrating.

Maybe some gold plating here would be to (1) show a better error message when you click away from keeweb to another tab, (2) save changes using AJAX when keepass file is changed instead of on a schedule or by default off, (3) provide some onboarding help to show people how it works.

Thanks for an amazing feature! I look forward to using this. 🤗