Skip to content
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

Feature Request: Disabling file uploads for specific users #2696

Closed
farson2003 opened this issue Apr 3, 2013 · 10 comments
Closed

Feature Request: Disabling file uploads for specific users #2696

farson2003 opened this issue Apr 3, 2013 · 10 comments

Comments

@farson2003
Copy link

Some admins wish to share information with users. At the same time, admins may want to prevent users/groups from uploading any file.

This is a feature request. I do not need it urgently, but I can very well imagine many admins would wish such file upload restrictions for their users.

Please consider.

@jancborchardt
Copy link
Member

Hmm, does setting the storage to »0« actually set it to »nothing« or »unlimited«? @schiesbn? If it’s »unlimited«, it should probably be »nothing« instead, and the code for »unlimited« might be better »-1« or so.

@jancborchardt
Copy link
Member

In other words: @farson2003 did you try setting the storage for that user to something low like 0, or 1? Does that solve your problem?

@BernhardPosselt
Copy link
Contributor

@icewind1991

@RandolfCarter
Copy link
Contributor

@jancborchardt 0 seems to stand for default - when setting the quota to 0, then leaving and returning to the Users page, it gets set back to "Default".... which can be quite confusing, if there are some values with special meaning they should be set immediately I guess - that way the user at least has the chance to notice that some automatic changes are going on

The lowest quota to be effective seems to be "1", i.e. 1 Byte...

@farson2003
Copy link
Author

jancborchardt commented "did you try setting the storage for that user to something low like 0, or 1? Does that solve your problem?"

YES: I tried 1, and in principle that would be a rather primitive solution.
however, everytime a user then logs in and has a look at files the admin has shared with him, the user gets the yellow message at the top of the page: "Your storage is full, files can not be updated or synced anymore!".
Many users may find this confusing.

So this solution does work, but is not really elegant if we want to use it more professionally.

What do you think?

@ghost ghost assigned schiessle Apr 12, 2013
@jancborchardt
Copy link
Member

@farson2003 so what happens if you set it to 0?

@farson2003
Copy link
Author

@jancborchardt
As Randolfcarter wrote: " when setting the quota to 0, then leaving and returning to the Users page, it gets set back to "Default"

@jancborchardt
Copy link
Member

Ok, I guess @schiesbn or @blizzz need to check this out. :)

@schiessle
Copy link
Contributor

Indeed '0' was converted to 'default'. I changed the code to make it possible to set the user quota to zero. See Pull request #3244.

@farson2003 With ownCloud5 the yellow message only appears if a user tries to upload a file, informing him that he doesn't have enough free space. I think that should be fine.

MorrisJobke added a commit that referenced this issue May 7, 2013
schiessle pushed a commit that referenced this issue May 7, 2013
@the-question
Copy link

I don't know if I must create a new issue or not.
I have a very close problem. Your merge doesn't solve it. I want to disable creation of files or folders to a user, and setting quota to 0 only prevent him from uploading a file or a folder, but if this user uses OwnCloud "New" button, he can always create something.
So, I want the same result as chmod -w on user's files folder.

P.S: Sorry for my english, I'm french. And sorry if I haven't post in the right place, please redirect me.
Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants