#23650 closed enhancement (fixed)
make get_space_allowed() filterable
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 3.7 | Priority: | normal |
Severity: | normal | Version: | 3.4 |
Component: | Multisite | Keywords: | has-patch |
Focuses: | Cc: |
Description
When the blog_upload_space
option is set to 0
, instead of returning 0
, get_space_allowed()
returns the default value which is currently hardcoded to 50
in core.
As discussed in #18119 and committed in [19314], the function should return 0
if the option is set to 0
. However this was reverted in [19654] (see #19538). So I am not sure which is the desired behaviour.
The attached patch adds filters for the default value and for the returned value. This is useful for scenarios where you don't want it to fallback to 50
if the option is accidentally set to 0
, and you want to set your own default.
I can adjust the patch if the consensus is that an option of 0
should in fact return 0
.
Attachments (2)
Change History (9)
#3
@
12 years ago
I wonder if this actually needs there to be a filter for the default. That is basically just a fallback for when the blog_upload_space network-wide option doesn't exist, and it really really should exist. (It is also 100MB as of [20170], and this 50 should too become 100). There is so little logic in get_space_allowed() that a single filter at the bottom should be sufficient.
#4
@
12 years ago
I'm game for 23650.2.diff, any objections?
Moving to 3.7 for discussion. Patch applies ok