[wp-trac] [WordPress Trac] #32075: Only set WP_MAX_MEMORY_LIMIT by default when its greater than memory_limit

[WordPress Trac]

#32075: Only set WP_MAX_MEMORY_LIMIT by default when its greater than memory_limit
---------------------------------------------+-----------------------
 Reporter:  danielbachhuber                  |       Owner:  ocean90
     Type:  defect (bug)                     |      Status:  accepted
 Priority:  normal                           |   Milestone:  4.6
Component:  Bootstrap/Load                   |     Version:  3.2
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------

Comment (by jrf):

 Changes:

 * Reverted, but documented `256 * MB_IN_BYTES`.
 * Improved documentation of the `$context` parameter for the
 `wp_raise_memory_limit()` function - added information about possibility
 to use arbitrary context.
 * Improved return value of `wp_raise_memory_limit()`. Returns false if
 memory was not changed and new value if it was.
 * Carried over some documentation improvements which had been applied in
 the mean time to moved round code.
 * Minor improvement to the `image_memory_limit` filter documentation -
 precision of what passed parameter is.
 * Merged documentation of the `wp_convert_hr_to_bytes()` function with the
 previous documentation for `wp_convert_php_ini_bytes_to_int()`.
 * Use the `GB/MB/KB_IN_BYTES` constants in `wp_convert_hr_to_bytes()` as
 they are now available before the function is first used.
 * Minor documentation and spelling improvements in the new unit test file.

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