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

File sharing #3949

Closed
johntung opened this issue Jul 5, 2013 · 5 comments
Closed

File sharing #3949

johntung opened this issue Jul 5, 2013 · 5 comments

Comments

@johntung
Copy link

johntung commented Jul 5, 2013

I login as UserA and share a file with update permission called testing.xls to UserB. UserB logged to the system and made some changes. The problem is that UserB accepted the replacement warning but the file is not replaced. Instead, a file called testing (2).xls appears. If you click on that file, ownCloud tells you that it does not exist.

I believe that it is a bug. Please kindly check.

@MorrisJobke
Copy link
Contributor

cc @MTGap @icewind1991

@johntung
Copy link
Author

johntung commented Jul 8, 2013

There is nothing in your comment. Please advise.

@MorrisJobke
Copy link
Contributor

@johntung I've just pulled in the responsible persons

@karlitschek
Copy link
Contributor

@schiesbn Can you check if this still exists?

@PVince81
Copy link
Contributor

I tried the following steps:

  1. Login as userA
  2. Upload a file "test.txt".
  3. Share "test.txt" with userB with "can edit" permission
  4. Create a directory "testdir"
  5. Upload a file "test.txt" into "testdir".
  6. Share "testdir" with userB with "can edit" permission
  7. Login as userB
  8. Edit "/Shared/test.txt" with the inline text editor and save
  9. Edit "/Shared/testdir/test.txt" with the inline text editor and save
  10. Upload "test.txt" into "/Shared/testdir" to replace it.

In OC 5.0.13: At step 10, a file "test (2).txt" appears which can correctly be edited, no warning appear.
In OC6 beta 3 (master): At step 10, a file conflict dialog appears. If you choose to keep both files it will create "test (2).txt" which can be opened properly.

If at step 3) and step 6) you pick "can update" instead of "can edit", you will only be able to edit the files through the inline text editor (no upload).

It all seems to work, closing.

@johntung feel free to reopen if you still meet this issue. Thanks.

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

4 participants