v6 no longer supports sync size limits. Please bring that back.

Desktop
1

Expected behaviour

In v5 on MacOS, I was swamped by new folders that were automatically selected for synchronisation. Fortunately I could turn that off by setting the sync limit to 0 bytes.

In v6 this sync limit functionality is gone. So I’m left again with the situation that OwnCloud forces me to synchronise any new folder. That does not make sense. What is next: From the folders I did not select 1 is randomly selected every day? Owncloud decides for me what I will want to sync?

On top of that v6 also skipped virtual file system. I cannot find the option anymore.

Steps to reproduce

  1. Set up account and sync only 1 folder

  2. Let it sync. Folder is synced nothing more

  3. Create a new folder with 10 TB (to show the point) and sync again. The new folder is being copied - although I never selected it.

Server configuration

Operating system: Ubuntu

Web server: ?

Database: ?

PHP version: ?

ownCloud version: ?

Storage backend (external storage): ?

Client configuration

Client version: 6.0.3

Operating system: MacOS

OS language: EN

Qt version used by client package (Linux only, see also Settings dialog): -

Client package (From ownCloud or distro) (Linux only): -

Installation path of client: Default

Logs

Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.

Template for output < 10 lines

  1. Client logfile: Output of owncloud --logwindow or owncloud --logfile log.txt
    (On Windows using cmd.exe, you might need to first cd into the ownCloud directory)
    (See also ownCloud Documentation Overview :: Documentation for ownCloud (A Kiteworks Company) )

  2. Web server error log:

  3. Server logfile: ownCloud log (data/owncloud.log):

2

Isn’t this something to discuss with the dev team directly? Issues · owncloud/client · GitHub

3

The report ties both changes to ownCloud Desktop 6.0.3 on macOS, so the server is unlikely to control these settings. Testing the same account with the previous v5 client would isolate whether the missing 0-byte limit and virtual-files toggle are client regressions; which macOS version and 6.0.3 build are affected?