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
Display the blue sync-icon after adding some new folders/files to owncloud-sync-folder. So you know that owncloud-client starts working
Actual behaviour
Owncloud-client display the green check-icon, despite the fact that there are some new folders/files to sync. Looking at the logwindow you can detect that owncloud-client is already syncing the new files (or doing something with these new folders/files). Only if the files really start to copy to the server the icon changes to the blue one.
Steps to reproduce
Put some folders (about >300 MB) to owncloud-client sync-folder.
Look at the logwindow: owncloud-client starts checking the folderstructur or something, that is however part of the sync-process
The owncloud-icon in the panel display the green-check so you are not sure if the client is working or not.
Server configuration
Operating system: Ubuntu 13.04
Web server: apache
Database: MYSQL
PHP version: 5
ownCloud version:
Client configuration
Browser: Firefox
Operating system: Ubuntu 13.04
The text was updated successfully, but these errors were encountered:
Expected behaviour
Display the blue sync-icon after adding some new folders/files to owncloud-sync-folder. So you know that owncloud-client starts working
Actual behaviour
Owncloud-client display the green check-icon, despite the fact that there are some new folders/files to sync. Looking at the logwindow you can detect that owncloud-client is already syncing the new files (or doing something with these new folders/files). Only if the files really start to copy to the server the icon changes to the blue one.
Steps to reproduce
Server configuration
Operating system: Ubuntu 13.04
Web server: apache
Database: MYSQL
PHP version: 5
ownCloud version:
Client configuration
Browser: Firefox
Operating system: Ubuntu 13.04
The text was updated successfully, but these errors were encountered: