Akeeba Backup for WordPress

#27268 PHP memory_limit too low after update to 2.1.0.b1

Posted in ‘Akeeba Backup for WordPress’

This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

WordPress version

n/a

PHP version

n/a

Akeeba Backup version

n/a

Latest post by on Thursday, 06 April 2017 17:17 CDT

Monday, 06 March 2017 13:25 CST

klox7

Hello,

as said in title, I can't create backups after update to 2.1.0.b1. It says PHP memory_limit too low even though mine is set to 128. One version earlier was working fine.

Regards

Tuesday, 07 March 2017 01:32 CST

nicholas

You have a line in your wp-config.php file like this:

define( 'WP_MAX_MEMORY_LIMIT', '134217728' );

Change it to read

define( 'WP_MAX_MEMORY_LIMIT', '128M' );

and now everything will work just fine.

That's due to a bug in beta 1. It cannot parse memory limits given in absolute byte values, i.e. 134217728, but it can parse memory limits given in human readable number-followed-by-UOM format such as 128M or 131072K. This will be fixed in the next testing version.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 07 March 2017 03:18 CST

klox7

Hi, I already had it like this

define('WP_MEMORY_LIMIT', '128M');

I changed it to what you suggested but I still get error.

Cheers.

Edited by klox7 on 2017-03-07 03:18 CST

Tuesday, 07 March 2017 06:38 CST

nicholas

To the best of my knowledge that's the only user-defined constant which affects the memory limit. Can you please try the latest developer's release?

Nicholas K. Dionysopoulos

Lead Developer and Director

Thursday, 06 April 2017 17:17 CDT

System Task

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Edited by on 2017-04-06 17:17 CDT

Support