[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
Sat Feb 13 15:02:20 UTC 2016


#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:  Future Release
Component:  Bootstrap/Load          |     Version:  3.2
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+-----------------------------

Comment (by markoheijnen):

 Replying to [comment:10 jrf]:
 > Not 100% sure what you mean, but the default for the `$filtered_limit`
 is the `WP_MAX_MEMORY_LIMIT` constant which can be set in `wp-config.php`
 and defaults to `256M` or the `php.ini` memory limit, whichever is higher.

 Personally I don't like constants but I do get your point. Say I use a
 plugin that imports CSV's and that plugin will use this new method
 `wp_raise_memory_limit('csv')`. I will be able to increase it with
 `csv_memory_limit` to 512M when needed.

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


More information about the wp-trac mailing list