Currently, there is no way to give an "unlimited" value to the "Default total file size per user:" setting in the File Uploads settings menu.
When I set this setting to a value of 0, which is logical way of saying "the user has unlimited file space on this site", I receive the following two errors:
* The default file size limit must be a number and greater than zero.
* The default maximum file size per upload is greater than the total file size allowed per user
The install is a default 5.0-beta install, no additional modules or changes made.
| Comment | File | Size | Author |
|---|---|---|---|
| #24 | upload.admin_.inc_.zip | 1.95 KB | spike22 |
| #14 | 93154.drupal.upload.fixui-unlimited.patch | 4.5 KB | joachim |
| #13 | drupal5.patch | 3.78 KB | kleung11 |
| #8 | upload.usersize.patch | 3.89 KB | mfb |
| #6 | upload.usersize.patch | 1.17 KB | mfb |
Comments
Comment #1
webernet commentedComment #2
webernet commentedComment #3
webchick+1 to this. I've had to raise the upload limit on d.o 3 times since the ifac stuff got committed.
Comment #4
aclight commentedsubscribe
Comment #5
scoutbaker commentedsubscribe
Comment #6
mfbThe upload settings form limits us to 99999 MB (~100 GB) per user including the anonymous user. I attached a drupal 6 patch to allow 9999999 MB (~10 TB) per user; although if this won't be accepted in drupal 6 I should probably just fix via form alter. Of course unlimited is the real answer.
Comment #7
Susurrus commentedI think this is the wrong way to go about this. I think that a value of 0 should be allowed like Syn said, which is a common way of saying unlimited. A little bigger patch would be needed for this, but it wouldn't take too much work.
Comment #8
mfbHere's a patch adding the feature for drupal 7.
Comment #9
Susurrus commentedSo that patch handles settings the max file size to 0, but what about actually using that value in the upload validation code where the check against the user's total file quota usage is calculated? Since 0 really mean 999999999999..., I would think there needs to be some special logic to handle that.
Comment #10
mfbAs far as I can tell, the logic already handles a "zero" as unlimited correctly. I did some quick smoke testing and it seems to work, but it should have some more testing.
Comment #11
dries commentedCommitted to CVS HEAD. Thanks mfb. Rock on.
Comment #12
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #13
kleung11 commentedI backported the drupal7 patch that mfb made to Drupal5. Testing shows that it works correctly.
Comment #14
joachim commentedThis is a bug on 6 -- reopening.
A bug because the code clearly is written with this in mind:
but the UI is not.
Rerolled the patch from #8 above (but without the text on 'least restrictive limit' which is useful but patch creep).
Comment #15
joachim commentedOops. Setting to needs review.
Comment #16
jaypanBump - the quota can still not be set to zero in Drupal 6
Comment #17
TimG1 commentedsubscribing.
Comment #18
domosapiens commented+1 for this up. This would be very usefull.
Comment #19
Mateo1041 commentedSubscribing.
Comment #20
quitos commented+1
Comment #21
dddave commented+1 don't help nobody. If anybody wants this in, please review!
http://drupal.org/patch/review
Comment #22
akalata commentedTested, works for me in 6.19.
Comment #24
spike22 commentedI was thinking and searching about this and wondering why do the administrators need to restrict the total amount. There should be a choice to let them configure by themselves, not because of the system need. I personally agree with others that this choice should be in the core upload module too. The system shouldn't be that strict, and the admins should be able to choose the zero amount as unlimited. It's kinda freedom thing :) "If you want to limit, you can, but by default there isn't any limit..." If anyone still needs the modified upload.admin.inc file, than that can be found in the attachment (replace it with the original core's file and there u go).
Comment #25
kressin commented#8: upload.usersize.patch queued for re-testing.