[wp-trac] [WordPress Trac] #13307: 3.0 package size will cause memory limit problems

[WordPress Trac]

#13307: 3.0 package size will cause memory limit problems
-----------------------------+----------------------------------------------
 Reporter:  nacin            |        Owner:  nacin 
     Type:  defect (bug)     |       Status:  closed
 Priority:  highest omg bbq  |    Milestone:  3.0   
Component:  General          |      Version:  3.0   
 Severity:  blocker          |   Resolution:  fixed 
 Keywords:                   |  
-----------------------------+----------------------------------------------

Comment(by Denis-de-Bernardy):

 Replying to [comment:48 nacin]:
 > We're getting memory limit errors *downloading* the package. There is
 nothing we can do other than alter the size of the package.

 Yeah... I convinced of the same in 2007.

 Consider, for a moment, whether that that specific feedback might be
 erroneous, and whether what's really happening might not be what I
 described in #10611 -- i.e. related to clean-ups and unzips.

 But heck, don't take my word for it. I've been upgrading -- and supporting
 -- thousands of sites in the past years, using a zip that is larger than
 WP 3.0, occasionally on awkward platforms. You haven't. (Those few who
 have been testing almost certainly have good servers.) Just saying...

 Anyway, I've raised more tickets than I can count related to this problem.
 I've also fixed the issue on my end. (By splitting the zip in bite-sized
 chunks, if you need to know.) Considering your reply, the only answer I
 can think of is: good luck.

 Adding a short notice in the WP upgrade screen won't hurt though...

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/13307#comment:49>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software