-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Made the video channels limit (per user) server-wide configurable #4491
Made the video channels limit (per user) server-wide configurable #4491
Conversation
Implements Chocobozzz#3092 Also added a "quota bar" in the account's settings page
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have also added a "quota progress bar" for video channels in the account's settings page (screenshot 3). It's something I believe is useful to make users aware of this limitation, but I have the feeling it might not be self-explanatory, and therefore confusing. Your thoughts?
I think we should not display this quota, that is just a server limitation. Most users won't reach this limit, so adding another quota bar in the profile est maybe "too much".
That's what I figured out for the users. What about the admins (displaying this quota in the users administration tab)? |
I don't think it's worth the effort. As an admin, I don't think I'm interested in the number of channels per users. Other information like videos count/storage used by a user seems more useful. |
Noted. I'll get rid of that. |
Done. The original message has been edited to reflect the actual content of the PR. |
Thanks @Poslovitch |
Description
Per request in #3092, I have added a config option in the server config (
video_channels.max_per_user
) to allow server admins to choose how many video channels users are allowed to create. I have consequently added a field in the web config editor (screenshot 1). The default is kept at 20, and the value can go down to 1.Despite now being configurable, it correctly prevents the user from creating any further channels if exceeding the amount (screenshot 2).
Related issues
Implements #3092
Has this been tested?
Screenshots