#19538 closed defect (bug) (fixed)
Multi-site Upload Limit Stuck at 50MB
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 3.3.1 | Priority: | normal |
Severity: | critical | Version: | 3.3 |
Component: | Upload | Keywords: | has-patch commit |
Focuses: | Cc: |
Description ¶
Hey all,
This has been confirmed by multiple users. After upgrading to WP3.3, all sites on the multi-site, except for the initial site / (or /blog/) are stuck at a 50MB upload limit, if upload limiting is enabled.
This took effect as soon as the upgrade to WP3.3 was complete. Changing the site's individual upload limit, as well as changing the network-wide limit, took no effect. This occurs with all plugins disabled, as well.
This is a critical bug for us, as our sites cannot upload any media with the cap so low.
Commits (4)
- [[19639]] Better checking for values for multisite upload limits. see #19538 for trunk.… by @nacin 13 years ago
- [[19645]] Better checking for values for multisite upload limits. fixes #19538 for 3.3… by @ryan 13 years ago
- [[19652]] Revert half of [19639]. If the blog_upload_space site_option is '0', restore 50 as a default. see #19538.… by @nacin 13 years ago
- [[19654]] Revert half of [19639]. If the blog_upload_space site_option is '0', restore 50 as a default. see #19538 for 3.3.… by @nacin 13 years ago
Pull Requests
- Loading…
Change History (25)
#2
@
13 years ago
Network setting was set to "1024" (no quotes)
Per-site setting I tried with both "100" and a blank value
#3
@
13 years ago
- Keywords has-patch added; reporter-feedback removed
I entered those values in my dev install and the dashboard of the subsite says 100MB of space.
If I leave the option empty on the individual site I do get the 50MB.
#9
@ Lead Developer
13 years ago
19538.hotfix.diff is a patch for the Hotfix plugin. Can someone test?
#10
@ Lead Developer
13 years ago
We're doing === ''
and === false
to avoid catching '0'
/ 0
, I imagine. In that case, we can just move to is_numeric()
.
#12
@ Lead Developer
13 years ago
- Keywords commit added
Marking as commit for the 3.3 branch, after additional review.
#14
@ Lead Developer
13 years ago
[19639] means that a site option of 0 will enforce the 0. While it makes it consistent, I don't know if that's a good change for a point release.
#15
@ Lead Developer
13 years ago
This broke some unit tests. We should also add new ones to account for any changes.
#16
@ Lead Tester
13 years ago
- Owner set to ryan
- Resolution set to fixed
- Status changed from new to closed
In [19645]:
#17
@ Lead Developer
13 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
Re-opening for comment:14 and comment:15. I would like to change back to empty() || is_numeric()
for the second conditional for 3.3.1 only, as that attempt at standardization can introduce a change in behavior.
#19
@ Lead Developer
13 years ago
The piece reverted in [19652] looked good. However, it introduces a change in a point release that could disable uploads for an entire network. Let's not include that in the 3.3 branch.
#21
@ Lead Developer
13 years ago
- Resolution set to fixed
- Status changed from reopened to closed
Any further fixes should be a new ticket for 3.4.
What value are you filling in for the limit?