You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I've noticed that the option filesystem_check_changes=1 is not having the same behavior as in the previous version when using a shared folder.
Please consider the following scenario:
In the server config, filesystem_check_changes=1
There are 2 users in a server, John, and Jane.
John shares the folder with Jane.
There is a change outside Nextcloud, a new file in the shared folder.
Log as Jane, access the folder and you will find it empty. [while expecting to see a new file]
Then log as John (shared folder owner) and you will find the new file there. (expected behavior)
Again as Jane, go to the shared folder and the new file will appear.
It looks like, unlike in the previous version, the filesystem_check_changes is only working for user-owned folders, while in previous versions it was also triggering the updates in shared folders as well.
Thank you!
Steps to reproduce
Configure your installation with the option 'filesystem_check_changes' => 1
Create 2 new users
With user1, share a folder to user2
Add or delete a new file in the shared folder, outside Nextcloud
Check with user2 the contents of the shared folder - The changes will not be reflected.
Navigate/refresh the shared folder again, with user1 - The changes will be synchronized.
Check again the folder with user2 - The changes will be there, as expected.
Expected behaviour
As in previous versions, with the option filesystem_check_changes set to 1, any user accessing any folder (even owned by other users) should make Nextcloud check for filesystems changes.
Actual behaviour
The filesystem_check_changes seem to apply only to folders owned by the current user.
Server configuration
Operating system:
CentOS, using the latest Nextcloud Docker image ID c664af0d9c67
Web server:
Apache 2.4
Database:
MariaDB 10.5.5
PHP version:
Version: 7.4.12
Nextcloud version: (see Nextcloud admin page)
20.0.2
Updated from an older Nextcloud/ownCloud or fresh install:
Updated
...
{"reqId":"gKs243baNCCy6wxraGu9","level":0,"time":"2020-11-22T14:15:11+00:00","remoteAddr":"<MASKED>","user":"--","app":"no app in context","method":"GET","url":"/ocs/v2.php/apps/notifications/api/v2/notifications","message":"OC_App::registerLogIn() is deprecated, please register your alternative login option using the registerAlternativeLogin() on the RegistrationContext in your Application class implementing the OCP\\Authentication\\IAlternativeLogin interface","userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36","version":"20.0.2.2"}
{"reqId":"YBZen8UiO6I9DBKDDQG7","level":0,"time":"2020-11-22T14:15:11+00:00","remoteAddr":"<MASKED>","user":"--","app":"no app in context","method":"GET","url":"/ocs/v2.php/apps/notifications/api/v2/notifications","message":"OC_App::registerLogIn() is deprecated, please register your alternative login option using the registerAlternativeLogin() on the RegistrationContext in your Application class implementing the OCP\\Authentication\\IAlternativeLogin interface","userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36","version":"20.0.2.2"}
Browser log
Browser log
Empty logs
The text was updated successfully, but these errors were encountered:
Found a solution. I'm using version 21.0.2. I've had today the same problem. I've copied data on webserver from old to new nextcloud-installation with file-copy and not in nextcloud GUI and nothing was shown in my shared-folder. So if you rename after that the shared folder, it will be updated and all files are visible. After that you can rename it again.
Hello,
I've noticed that the option filesystem_check_changes=1 is not having the same behavior as in the previous version when using a shared folder.
Please consider the following scenario:
It looks like, unlike in the previous version, the filesystem_check_changes is only working for user-owned folders, while in previous versions it was also triggering the updates in shared folders as well.
Thank you!
Steps to reproduce
Expected behaviour
As in previous versions, with the option filesystem_check_changes set to 1, any user accessing any folder (even owned by other users) should make Nextcloud check for filesystems changes.
Actual behaviour
The filesystem_check_changes seem to apply only to folders owned by the current user.
Server configuration
Operating system:
CentOS, using the latest Nextcloud Docker image ID c664af0d9c67
Web server:
Apache 2.4
Database:
MariaDB 10.5.5
PHP version:
Version: 7.4.12
Nextcloud version: (see Nextcloud admin page)
20.0.2
Updated from an older Nextcloud/ownCloud or fresh install:
Updated
Where did you install Nextcloud from:
Latest docker image. https://hub.docker.com/_/nextcloud
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
**Are you using external storage, if yes which one: sftp
Are you using encryption: no
Are you using an external user-backend, if yes which one: None
LDAP configuration (delete this part if not used)
LDAP config
Client configuration
Browser:
Operating system:
MacOS 10.15.7
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
The text was updated successfully, but these errors were encountered: