[wp-trac] [WordPress Trac] #29341: Raise default value for WP_MEMORY_LIMIT in wp-includes/default-constants.php

[WordPress Trac]

#29341: Raise default value for WP_MEMORY_LIMIT in wp-includes/default-
constants.php
------------------------------------+------------------------------
 Reporter:  DavidAnderson           |       Owner:  (none)
     Type:  enhancement             |      Status:  new
 Priority:  normal                  |   Milestone:  Awaiting Review
Component:  Bootstrap/Load          |     Version:  4.0
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+------------------------------

Comment (by tomsommer):

 Due to larger and more complex plugins, there are now a great number of
 online articles that instruct users how to set `WP_MEMORY_LIMIT` and
 `WP_MAX_MEMORY_LIMIT` to big values. This should not be a thing users have
 to deal with.

 The better option in 2019 would be leave memory-management up to the
 Sysadmin, PHP and the memory_limit setting from php.ini.
 Currently there is no way for a server/sysadmin to impact
 `WP_MEMORY_LIMIT` above `40M` and that should not be the case - WordPress-
 core itself does not know best what `memory_limit` to use.

 I propose always setting `WP_MEMORY_LIMIT` to `$current_limit` by default,
 unless `is_multisite()` is true or `WP_MEMORY_LIMIT` is already defined.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/29341#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform