-
Notifications
You must be signed in to change notification settings - Fork 20
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
Confusing errors on folder with don't-Sync setup #193
Comments
I'm not sure if my issue belongs here or to the Desktop-Client but since it was suggested here: https://help.nextcloud.com/t/administrative-control-to-block-folders-or-files-from-being-syncd-by-clients/29214/12 to use File access control to prevent syncing from the server (not the client!), I post this here. Our intention is to prevent syncing of some folder/files without any setup on the client side. But since this is a management decision no errors or warnings should ever irritate any brave user. I'm sure many organizations have such requirements and do not like to increase support calls to their IT department 😄 |
This is not the intended way this app works. The designed case is to have it still locally. |
Can we get rid of any errors shown in the desktop client, at least? |
No because for all other cases it's important to know that the sync didn't work |
So since errors are not what we can offer to the management, what is the preferred way to prohibit the sync of files/folders from the server side? |
I would like to joint this issue for a related case of nuisance logging/errors. I've added a server-side rule to globally ignore nuisance files that are saved in the working directory. AutoCAD creates autosave/restore files [filename].bak, *.dwl and *.dwl2 in the working directory which are constantly written when a file is open, resulting in a ton of sync churn across the whole server and all users. I've added this rule: Logs are now full of 'Error' level access denied log entries. The log entries look like legitimate errors and the presentation of the error in the admin web log viewer doesn't indicate the source of the error without downloading the log and reading the full entry. The error entries all refer to DAV (which I suppose is technically true), but there is no mention of this app as the true source. Preferred Behavior: |
Just a +1. I need to make sure a file is edited in Collabora, while the others are client-synced. I created a file access control rule to deny the sync of that file in the NC Client, but now the client says the sync is in error. |
Same here. A flow set to prevent syncing should NOT trigger an Error. Simply because it isn't. |
Steps to reproduce
Expected behaviour
Actual behaviour
Server configuration
Operating system: Linux 4.19.0-11-amd64 #1 SMP Debian 4.19.146-1 (2020-09-17) x86_64
Webserver: Apache/2.4.38 (Debian) (fpm-fcgi)
Database: mysql 10.3.27
PHP version: 7.4.15
Modules loaded: Core, date, libxml, openssl, pcre, zlib, filter, hash, Reflection, SPL, session, standard, sodium, cgi-fcgi, mysqlnd, PDO, xml, apcu, bcmath, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, gmp, iconv, igbinary, imagick, intl, json, exif, msgpack, mysqli, pdo_mysql, pdo_sqlite, apc, posix, readline, shmop, SimpleXML, sockets, sqlite3, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, zip, Phar, memcached, Zend OPcache
Nextcloud version: 20.0.8 - 20.0.8.1
Updated from an older Nextcloud/ownCloud or fresh install: updated
Where did you install Nextcloud from: tgz from Nextcloud
Signing status:
List of activated apps:
Nextcloud configuration:
Are you using external storage, if yes which one: no
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
Client configuration
Desktop-Client Version 3.1.3 (openSuse)
Operating system:
Logs
Nextcloud log (data/owncloud.log)
Browser log
The text was updated successfully, but these errors were encountered: