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

Client synchronisation is not always triggered when a user changes contents of a shared folder #1499

Closed
TalviT opened this issue Oct 10, 2019 · 4 comments

Comments

@TalviT
Copy link

TalviT commented Oct 10, 2019

Expected behaviour

When one user changes the contents of a shared folder, the affected files are synchronized by the client for the other users.
In other words, if the activation feed says that a file has been changed, it should trigger synchronization.

Actual behaviour

Users who are not the owner of the shared folder will only see the changes in the web browser or the client's activity feed, but their files will remain unchanged.

Steps to reproduce

Setup:

  • User "Test 1" is the owner of the folder "Shared".
  • Test 1 shares Shared with user "Test 2".
    -> Test 2 sees in the web browser and in the activity feed of the client that Test 1 shared Shared with Test 2.
    -> The folder Shared appears immediately in the directory of Test 1.
    -> The Shared folder does not appear in the Test 2 directory.

Further testing steps:

  • Test 2 creates a file "foo" in the root directory or Test 2 forces a synchronization in the client or Test 2 restarts the client.
    -> The shared folder Shared appears.

  • Test 2 creates a file "file_from_test_2" in Shared.
    -> Test 1 gets the file immediately.

  • Test 1 deletes this file again.
    -> Test 2 sees in the web browser and in the activity feed of the client that the file has been deleted.
    -> The file is not deleted from the directory.

  • Test 2 deletes the file "foo" from the root directory or Test 2 forces a synchronization in the client or Test 2 restarts the client.
    -> The Shared folder is empty again.

Client configuration

Client version: 2.5.3 and 2.6.0

Operating system:
Manjaro Linux

OS language:
German (de_DE)

Qt version used by client package:
5.13.0 (distro), 5.12.1 (appimage), 5.12.5 (flatpak)

Client package:
distro package (v2.5.3), AppImage from Nextcloud (v2.6.0) and Flatpak (flathub – v2.6.0).

Installation path of client:
Default from package manager/download directory in case of appimage?

Server configuration

Nextcloud version:
17.0.0

@TP75
Copy link

TP75 commented Oct 11, 2019

@FlexW
Copy link

FlexW commented May 26, 2021

Does this issue still persist in the most recent version (3.2.1)?

@github-actions
Copy link

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

@github-actions github-actions bot added the stale label Jun 24, 2021
@github-actions
Copy link

github-actions bot commented Jul 8, 2021

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!

@github-actions github-actions bot closed this as completed Jul 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants