Multisite upload settings are inconsistent

[danielbachhuber]

"Site upload space" is indicated in MB whilst "Max upload file size" is indicated in KB.

It would be useful to standardize on MB.

[jeremyfelt]

+1

The KB setting threw me for a second the other day. Especially when larger and larger uploads seem to be more common.

[bansod_deven]

Changed the indicators to MB

[bansod_deven]

Added a Patch. Changed the max File Upload size 'Indicators on the Form' to MB.
Did not change it in the Database. As the Value in Database(which is in KB) may be used by other Functions.

P.S. : The Max Upload File size needs to be still less than the PHP.ini's Settings for that. For increasing that you may need to change the settings of php.ini only

[bogdand]

fixed step incrementation

[bogdand]

Hi guys,

Tested the patch and everything seem to work ok. I changed the incrementation from 0.001 to 1

[jeremyfelt]

Thanks for the patches @banson_deven and @bogdand. These initial changes get us close. I've expanded a bit in 27224.3.diff.

• When storing fileupload_maxk, force absint() when converting POSTed MB to KB. I don't think we want to shift to float in the database after storing int for so long.
• Adjust all 3 areas where fileupload_maxk is communicated throughout core. Use ceil() to round up to the nearest integer. The default has been 1500KB, which will calculate to 1.46MB. Using round() would round down to 1MB by default and could cause confusion.
• There was one place - network settings - where the default site option for fileupload_maxk was 300, even though it is set to 1500 in the network schema. I changed this to be 1500 instead.

Note: This change does mean that a very precise DB setting such as 1234(KB) will now become a max size of 2MB and if re-saved from the settings screen will become a DB setting of 2048(KB).

I don't think this fits right now, but in a future network settings screen, it may be interesting to allow specification of unit in addition to the number— 1GB, 200MB, 20000KB, etc...

And for the sake of history. It appears the decision to use KB was made circa 2005 in or around ​mu:165

[jeremyfelt]

This feels strange. It would be nice to store the value as bytes and not have to do the math in multiple places. For that we'd have to deprecate the fileupload_maxk setting and go with fileupload_max or something.

[jeremyfelt]

I think we need to transition to storing this data as number of bytes rather than kilobytes. This will allow us to be much more flexible. I'm going to push to future release, but would be happy to test and help get into 4.1 if input on approach and a patch can line up.

[Presskopp]

related: #55662