Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

over quota handling in different UI #998

Closed
a-schild opened this Issue · 6 comments

5 participants

@a-schild

I had my owncloud account in a over quota status (11.3GB used of the default 10GB)
I did see that most syncs have not been working as the files never showed up the in web UI.

  • The webUI did not mention that fact, I think we should/must informa then user about this
  • Perhaps send a mail to the user mentioning that the quota is almost used up, and one when the quota is completely used
  • In the various sync clients (Linux + Windows) the status was always "Sync completed", no mentioning that it could not sync because of the over quota condition!
  • In the Android client I just got the error "Upload ... failed", no reason why
@dragotin dragotin was assigned
@DeepDiver1975

@danimo @dragotin is the handling of http 507 already implemented?
@MTRichards can you talk to the mobile devs to add http status code 507?
@jancborchardt your ux opinion please THX

@dragotin
Owner

quota handling should fine in the client with 1.1.4 and later.

@davivel
Collaborator

In the Android app we have to do some improvements with the error information.

@a-schild

On serverside I have seen http status 507 is returned when over quota
so it seems to be a thing about showing the error to the user

@jancborchardt
Collaborator

Regarding the web UI, a notification (the yellow one on top) on low storage or full storage is probably in order:

  • »Your storage is almost full (90%)
  • »Your storage is full, files can not be updated or synced anymore!«

When clicked, it will go to Personal settings, where the storage bar is.

@DeepDiver1975

as #1059 is merged now and the client dev teams are aware of this (or even fixed this already) I'll close that one.

From my point of view backport stable45 is out of scope due to the size of the change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.