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

filesystem_check_changes doesn't work with group folders #787

Open
DragonQ opened this issue Mar 6, 2020 · 4 comments
Open

filesystem_check_changes doesn't work with group folders #787

DragonQ opened this issue Mar 6, 2020 · 4 comments
Labels
1. to develop Issues that are ready for development enhancement

Comments

@DragonQ
Copy link

DragonQ commented Mar 6, 2020

I have filesystem_check_changes set to 1 in my Nextcloud config.php. This means when I create or edit files in my Nextcloud data directory via a Samba share, Nextcloud notices the changes and updates its database accordingly. However, if I add or edit a file in a group folder, Nextcloud does not notice the change.

Is this a bug? I am not sure how Nextcloud decides which directories to keep track of when this option is enabled.

@razorrazor
Copy link

razorrazor commented Dec 2, 2020

I have the same problem. I recently realized that files uploaded to group folders outside NC are not detected by NC.
Is there any workaround?

I think if GroupFolders is integrated with NC, the parameter 'filesystem_check_changes' => 1 should be taken into consideration by GroupFolders App...

@ryan4559
Copy link

ryan4559 commented Feb 7, 2021

Same problem here. Shared folders can't update.
nextcloud/server#24287

@pierreozoux pierreozoux added 0. Needs triage Issues that need to be triaged enhancement labels Mar 14, 2021
@razorrazor

This comment was marked as duplicate.

@joshtrichards joshtrichards changed the title filesystem_check_changes doesn't work with group folders filesystem_check_changes doesn't work with group folders Sep 10, 2024
@provokateurin
Copy link
Member

Likely needs a fix similar to nextcloud/server#28377

@provokateurin provokateurin added 1. to develop Issues that are ready for development and removed 0. Needs triage Issues that need to be triaged labels Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop Issues that are ready for development enhancement
Projects
None yet
Development

No branches or pull requests

5 participants