Make WordPress Core

Opened 15 years ago

Closed 15 years ago

Last modified 11 years ago

#19538 closed defect (bug) (fixed)

Multi-site Upload Limit Stuck at 50MB

Reported by: wspnut Owned by: ryan
Priority: normal Milestone: 3.3.1
Component: Upload Version: 3.3
Severity: critical Keywords: has-patch commit
Cc: Focuses:

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.

Attachments (3)

19538.diff (518 bytes ) - added by wpmuguru 15 years ago.
19538.2.diff (666 bytes ) - added by wpmuguru 15 years ago.
19538.hotfix.diff (870 bytes ) - added by nacin 15 years ago.

Download all attachments as: .zip

Change History (25)

#1 @wpmuguru
15 years ago

  • Keywords reporter-feedback added

What value are you filling in for the limit?

#2 @wspnut
15 years ago

Network setting was set to "1024" (no quotes)

Per-site setting I tried with both "100" and a blank value

#3 @wpmuguru
15 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.

@wpmuguru
15 years ago

#5 @wspnut
15 years ago

Patch fixed it. Thanks wpmugru.

@wpmuguru
15 years ago

#6 @wpmuguru
15 years ago

19538.2.diff also retains the support for the 0 upload limit.

#7 @anointed
15 years ago

Patch solved the problem for me. Thank you wpmugru!

#8 @ocean90
15 years ago

  • Milestone Awaiting Review3.3.1

Related: #18119/r19314

@nacin
15 years ago

#9 @nacin
15 years ago

19538.hotfix.diff is a patch for the Hotfix plugin. Can someone test?

#10 @nacin
15 years ago

We're doing === '' and === false to avoid catching '0' / 0, I imagine. In that case, we can just move to is_numeric().

#11 @nacin
15 years ago

In [19639]:

Better checking for values for multisite upload limits. see #19538 for trunk.

#12 @nacin
15 years ago

  • Keywords commit added

Marking as commit for the 3.3 branch, after additional review.

#13 @wpmuguru
15 years ago

That looks fine to me.

#14 @nacin
15 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 @nacin
15 years ago

This broke some unit tests. We should also add new ones to account for any changes.

#16 @ryan
15 years ago

  • Owner set to ryan
  • Resolutionfixed
  • Status newclosed

In [19645]:

Better checking for values for multisite upload limits. fixes #19538 for 3.3

#17 @nacin
15 years ago

  • Resolution fixed
  • Status closedreopened

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.

Last edited 15 years ago by nacin (previous) (diff)

#18 @nacin
15 years ago

In [19652]:

Revert half of [19639]. If the blog_upload_space site_option is '0', restore 50 as a default. see #19538.

#19 @nacin
15 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.

#20 @nacin
15 years ago

In [19654]:

Revert half of [19639]. If the blog_upload_space site_option is '0', restore 50 as a default. see #19538 for 3.3.

#21 @nacin
15 years ago

  • Resolutionfixed
  • Status reopenedclosed

Any further fixes should be a new ticket for 3.4.

This ticket was mentioned in Slack in #core by boone. View the logs.


11 years ago

Note: See TracTickets for help on using tickets.