[wp-trac] [WordPress Trac] #32075: Only set WP_MAX_MEMORY_LIMIT by default when its greater than memory_limit
WordPress Trac
noreply at wordpress.org
Thu Apr 23 12:33:45 UTC 2015
#32075: Only set WP_MAX_MEMORY_LIMIT by default when its greater than memory_limit
-----------------------------+-----------------------------
Reporter: danielbachhuber | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Bootstrap/Load | Version: 3.2
Severity: normal | Keywords:
Focuses: |
-----------------------------+-----------------------------
Even when `memory_limit` is set to 1GB or greater, WordPress will set
`WP_MAX_MEMORY_LIMIT` to `256MB` unless you've explicitly defined the
constant. However, unless the developer is already aware of this, the
constant can unintentionally break imports and other processes. I'd expect
WordPress to respect the value set in `memory_limit`.
The constant was introduced in r17749
Previously:
* https://github.com/Automattic/vip-quickstart/issues/398
* https://twitter.com/nacin/status/575317779793985536
--
Ticket URL: <https://core.trac.wordpress.org/ticket/32075>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list