Title: respecting WP memory limit
Last modified: August 20, 2016

---

# respecting WP memory limit

 *  Resolved [Viktor Szépe](https://wordpress.org/support/users/szepeviktor/)
 * (@szepeviktor)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/respecting-wp-memory-limit/)
 * /updraftplus.php:102
    `@ini_set('memory_limit', '192M');`
 * please respect these defines:
    WP_MEMORY_LIMIT, WP_MAX_MEMORY_LIMIT
 * Thanky you!!
 * syslog:
    Mar 30 20:57:59 mail suhosin[4202]: ALERT – script tried to increase
   memory_limit to 201326592 bytes which is above the allowed value (attacker ‘224.0.0.0’,
   file ‘/var/www/vk.com/server/wordpress/wp-content/plugins/updraftplus/updraftplus.
   php’, line 102)
 * [http://wordpress.org/extend/plugins/updraftplus/](http://wordpress.org/extend/plugins/updraftplus/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [David Anderson / Team Updraft](https://wordpress.org/support/users/davidanderson/)
 * (@davidanderson)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/respecting-wp-memory-limit/#post-3611723)
 * Hi Viktor,
 * Thanks for the report.
 * From my reading of WordPress’s source code, it looks like only WP_MAX_MEMORY_LIMIT
   would be relevant here. The other is the initial value, but only this one indicates
   what we’re allowed to attempt raising it to.
 * I’ve changed the relevant line now to use WP_MAX_MEMORY_LIMIT instead of the 
   hard-coded 192M. You can update to the trunk version, or alternatively hand-fix
   your copy until it is released.
 * Thanks again,
    David
 *  Thread Starter [Viktor Szépe](https://wordpress.org/support/users/szepeviktor/)
 * (@szepeviktor)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/respecting-wp-memory-limit/#post-3611865)
 * Thank you!
    Updraft runs on more websites listed here: [online1 webdesign](http://www.online1.hu/webdesign/)
 *  Plugin Author [David Anderson / Team Updraft](https://wordpress.org/support/users/davidanderson/)
 * (@davidanderson)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/respecting-wp-memory-limit/#post-3611878)
 * Hi Viktor,
 * Thank you.
 * Would you be interested in translating UpdraftPlus into Hungarian?
 * [http://updraftplus.com/translate/](http://updraftplus.com/translate/)
 * Best wishes,
    David
 *  Thread Starter [Viktor Szépe](https://wordpress.org/support/users/szepeviktor/)
 * (@szepeviktor)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/respecting-wp-memory-limit/#post-3611893)
 * please find theme at [mirror.szepe.net](http://mirror.szepe.net/wordpress/updraftplus/)
 *  Plugin Author [David Anderson / Team Updraft](https://wordpress.org/support/users/davidanderson/)
 * (@davidanderson)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/respecting-wp-memory-limit/#post-3611896)
 * Thank you, that’s great! That translation is now included in the plugin. I’m 
   emailing you now with a voucher you can use in our shop for $75 of free purchases
   this month: [http://updraftplus.com/shop/](http://updraftplus.com/shop/)
 * Best wishes,
    David

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘respecting WP memory limit’ is closed to new replies.

 * ![](https://ps.w.org/updraftplus/assets/icon-256x256.jpg?rev=1686200)
 * [UpdraftPlus: WP Backup & Migration Plugin](https://wordpress.org/plugins/updraftplus/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/updraftplus/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/updraftplus/)
 * [Active Topics](https://wordpress.org/support/plugin/updraftplus/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/updraftplus/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/updraftplus/reviews/)

## Tags

 * [limit](https://wordpress.org/support/topic-tag/limit/)

 * 5 replies
 * 2 participants
 * Last reply from: [David Anderson / Team Updraft](https://wordpress.org/support/users/davidanderson/)
 * Last activity: [13 years, 1 month ago](https://wordpress.org/support/topic/respecting-wp-memory-limit/#post-3611896)
 * Status: resolved