Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lost content on failed writes #44

Open
loleg opened this issue Dec 11, 2014 · 1 comment
Open

Lost content on failed writes #44

loleg opened this issue Dec 11, 2014 · 1 comment

Comments

@loleg
Copy link

loleg commented Dec 11, 2014

Realms should return to the Edit screen in case there is any problem saving the content, notifying the user (as with the logged out message) to avoid data loss.

In my installation a user began reporting lost content. No errors, no popups, just edits that were gone as soon as she clicked Publish. In trying to reproduce the problem, I noticed erroneous permissions in the filesystem. Instead of deploy:deploy the owner became root:root on some of the files.

This is likely because I am synchronising the Git repository using an external git process as well as Realms. To me the ability to do this is one of the top features of the wiki. I am now ensuring that permissions are being correctly set, however the wiki interface must do everything possible to avoid data loss: in this case, at least alerting the user if the save did not succeed.

@allanbarklie
Copy link

I'm experiencing this lost content problem occasionally.
I haven't pinned down what usage pattern provokes it.
I'm running a docker container built from the current head on docker for windows with a host folder mounted to /home/wiki/data.

So far I've been able to rescue my content by bringing up chrome developer tools and copying it out of the local storage field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants