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

v4.5.0: Undo function makes sync experience suboptimal #51

Closed
msrex opened this issue Oct 23, 2012 · 5 comments
Closed

v4.5.0: Undo function makes sync experience suboptimal #51

msrex opened this issue Oct 23, 2012 · 5 comments

Comments

@msrex
Copy link

msrex commented Oct 23, 2012

when you upload a file and select to overwrite the existing file, it does not create a new version immediately, but creates temporarily for the undo functionality a file (2). If you wait for a while until you reload the page, that file is being synced to the desktop or displayed in the webfrontend or mobile app. Then, after you reload the page, this change is being reverted and a newer version of the original file is being created.
This is confusing.
I propose to change this to the immediate creation of a new version with a notice in the yellow pop-up at the top of the screen telling the user that a new version was created.

Reproduction:

  1. create a file (e.g. hello) with the webfrontend
  2. on the local desktop create a file with the same name but different content
  3. upload the file via the upload in the webfrontend
  4. DO NOT RELOAD THIS PAGE!
  5. in a second browser or with the mobile client view the directory; or sync to your local desktop with the owncloud client
@DeepDiver1975
Copy link
Member

workaround will go live with OC5: undo will be removed

@msrex
Copy link
Author

msrex commented Feb 8, 2013

So there will be no undo at all?

@karlitschek
Copy link
Contributor

We have a new trash app that replaces that feature

@msrex
Copy link
Author

msrex commented Feb 8, 2013

thank you!

@karlitschek
Copy link
Contributor

It's more powerful and doesn't have the bug that is described here anymore :-)

aditmeno pushed a commit to aditmeno/Aeolus that referenced this issue Apr 2, 2015
@lock lock bot locked as resolved and limited conversation to collaborators Aug 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants