We have a site which works fine under WordPress 3.1.3. I tried to update WordPress to 3.2.1 today, using a manual procedure of uploading files to my web host via FTP, which I’ve done successfully before. When I next tried to access wp-admin, the update was detected and I was asked to accept a database update. After I did, instead of being able to access wp-admin, I got the following fatal error:
Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate 122880 bytes) in /home/<USERNAME>/public_html/wordpress/wp-admin/includes/dashboard.php on line 710
Luckily I managed to roll back to 3.1.3 and got our site working again. But I’m now stuck at 3.1.3. Can anyone please explain what might be going on? An allowed memory size of 262144 bytes seems much too small.
I should mention that I’ve had fatal errors relating to memory size before now, although not ones that wiped out the whole site. Under version 3.1.3, I had needed to modify some files to increase maximum memory, since I had been seeing fatal errors about 32M of memory being exhausted whenever I tried to publish new pages. To get rid of them I had edited .htaccess, wp-config.php, wp-settings.php and default-constants.php in order to change WP_MEMORY_LIMIT to 64M.
When I upgraded WordPress to 3.2.1, I uploaded those amended files, with the exception of default-constants.php and wp-settings.php, which had been updated in 3.2.1, so I edited the new files to increase WP_MEMORY_LIMIT instead. I can’t see anything obvious that’s caused the problem.
I’d be really grateful for any suggestions about what the problem might be in version 3.2.1. I’m worried about being stuck at 3.1.3. This site belongs to a non-profit that I’m supporting. It’s very important that it stays operational, and we can’t afford any consultancy.
Thanks very much for any help.
- The topic ‘Upgrade to 3.2.1 caused crash with fatal error about memory size’ is closed to new replies.