-
Notifications
You must be signed in to change notification settings - Fork 671
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
Default sync root directory created every time accounts are loaded #10919
Comments
erikjv
added a commit
that referenced
this issue
Aug 17, 2023
Creating the default sync root is only needed at initial setup. If a user chooses to point all folders for Spaces outside that default sync root, and deletes the default sync root folder, it should not be re-created. Fixes: #10919
erikjv
added a commit
that referenced
this issue
Aug 23, 2023
Creating the default sync root is only needed at initial setup. If a user chooses to point all folders for Spaces outside that default sync root, and deletes the default sync root folder, it should not be re-created. Fixes: #10919
erikjv
added a commit
that referenced
this issue
Aug 24, 2023
Creating the default sync root is only needed at initial setup. If a user chooses to point all folders for Spaces outside that default sync root, and deletes the default sync root folder, it should not be re-created. Fixes: #10919
@fmoc could you specify the steps to recreate?
|
Use case 1:
|
Use case 2:
It's really a minor bug, but it deserved a fix. |
Passed in owncloud-client_5.0.0.11978-daily20230830 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pre-submission Checks
Describe the bug
See https://central.owncloud.org/t/default-folder-created-at-each-start/44101.
The default sync root directory is created over and over again if set.
Expected behavior
It makes no sense to create the directory every time. Users may not even use it at all but use a totally different base directory to synchronize their files.
Possible solutions:
I am in favor with the latter.
Steps to reproduce the issue
No response
Screenshots
No response
Logs
No response
Client version number
4.0.0.10896 on Ubuntu 22.04.
Desktop environment (Linux only)
No response
Client package version and origin (Linux only)
No response
Installation path (Windows only)
No response
Server information
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: