[wp-trac] [WordPress Trac] #14889: Memory Comparison Broken / WordPress Memory Limit

[WordPress Trac]

#14889: Memory Comparison Broken / WordPress Memory Limit
--------------------------+-------------------------------------------------
 Reporter:  hakre         |       Owner:                 
     Type:  defect (bug)  |      Status:  new            
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  3.0            
 Severity:  normal        |    Keywords:  has-patch      
--------------------------+-------------------------------------------------

Comment(by hakre):

 +1 for using a named and not an anonymous function (as this is not PHP
 5.3) - if at all.

 If you don't like the drawback of having additional code in the bootstrap
 (albeit the bootstrap's complexity can be reduced but it's normally
 argumented against it - probably it depends who brings things up) in
 _this_case_ this could be done if administrators are told that they MUST
 configure their memory limit in the M notation in both PHP.INI and
 wordpress configuration.

 From a real life standpoint this can work, some might wonder, but if it's
 documented, why not? Most will have the M notation anyway. And even if you
 uses gigabytes, you can pretty easily write them in megabytes 1G = 1024M.

 I already updated my
 [http://codex.wordpress.org/User:Hakre/Technical_Installation WordPress
 Technical Installation Checklist] as it looks like that this bug (in terms
 of strict data handling) is never been fixed.

 ----

 I my eyes it's even more important right now to remove the '''256M
 limitation''' by making that magic number configureable (at least), see
 #13847.

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