-
Notifications
You must be signed in to change notification settings - Fork 667
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
Deal with old, unsupported server versions #4523
Comments
Lets create a red warning pane on the activity view, pause the account and show a tray notification. @ckamm I can do the one in the activity view along with my work on the notification stuff. |
@dragotin Ok. As long as users will actually see the message before they can reactivate their folders that's fine with me. |
* A tray message on every start up * Red message in account settings * Folders are paused when the server version switches to an unsupported one
Pull request: #4531 |
Add warnings for old server versions #4523
Merged.. |
Why is it necessary to notify every single time the client starts up?? Just let me tell the client that I'm happy with my server and from then on don't worry about it! OwnCloud server keeps adding features that I don't care about, so it's a pain to keep updating it, but the current server works completely fine. Now, every time we start up we have to manually tell the client that everything is alright. May have to search for a different client instead then, or back up the client version and freeze on that. |
Currently one can try to use the client with arbitrary old and unsupported server versions (see https://github.com/owncloud/core/wiki/Maintenance-and-Release-Schedule).
Since we don't even notify users about potential problems, they assume everything works. Then, when something breaks, the assumption is that the client has a bug.
Instead, we should be very upfront about potential problems (and dangers! it's untested!) of using a new client with an outdated server. There should be a persistent warning on such accounts. We should initially pause accounts like that too. Then users have to explicitly enable them and are aware of the potential problems.
The text was updated successfully, but these errors were encountered: