WP 3.2.1. problem out of memory

In that case, there’s a problem with the server configuration.

come on, why server problems. the 3.1.3 work veru well… I think the wordpress programmers dont see the problem in 3.2.1

WordPress 3.2 underwent more than 2 months of testing. This issue – whatever it is – is specific to your site/server/install.

mmm I think 2 month and still put php.ini and improve the memory limit is not good work…

HEY everybody look this fixed……

As several people have mentioned to me, WordPress has released a major update (version 3.2) to their software and a minor update (3.2.1). But I had still not updated my site to use the newest version and had not checked to see if my wp_mem128.patch patch was still needed to avoid the issues with a suhosin memory limit of less than 256 MB. Or even if it still worked.

I apologize for my delay, but I’ve now caught up to the leading edge of the official WordPress software updates. I found that there was a small rewrite in the WordPress code regarding how it increases the memory_limit. My previous patch works only up to version 3.1.4. With WordPress version 3.2, the software still tries to increase the memory limit to 256 MB, but that size is no longer hard coded in several different source files. The developers have created a variable named WP_MAX_MEMORY_LIMIT in the wp-includes/default-constants.php file. All of the places where the WordPress software wants obtain the maximum memory limits now reference this one variable. This is certainly a big improvement in program maintainability.

The net result, for those of us who use WordPress on a platform which limits its memory use to less than 256 MB, is that there is now only one place where that limit must be changed. For those who prefer to use a scripted update rather than a manual edit, I’ve created a new version of my patch file to set this variable to 128 MB. You are welcome to download it using this link: wp_mem128_3.2.patch

Here is an outline of how I updated the WordPress version from 3.1.2 to 3.2.1.

1.Backup the database and existing website files.
2.Login to the server via SSH.
3.Login to WordPress as the administrator.
4.Use the “Automatic Update” function.
5.From the SSH session, change to the root of the WordPress installation directory.
6.Execute the “patch -p0 < wp_mem128_3.2.patch” command.
7.Verify that the patch command completed without significant errors.
8.Switch back to the WordPress admin browser.
9.Return to the Dashboard.
10.Update the WordPress database version.

I Haven’t experienced this problem again so far after adding the following to the .htaccess file:

php_value memory_limit 64M

And this to wp-config.php:

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

^^ That didn’t work. I’m assuming that a change must be done through the host to provide a permanent fix for the problem.

Here it is: (Godaddy Specific)

First, determine the php memory limit for your host. You can do this by looking at your control panel, directly from the phpinfo file, or by installing the ServerBuddy plugin from the WordPress plugin directory.

If your memory limit is 32mb, then you’re SOL unless you upgrade your hosting plan – however, if you have more than that you can fix it…

PHP memory through my hosting plan maxes at 256M, however WordPress could only utilize 32M.

Prep Steps:
Get FileZilla – set up your FTP info and save.
Get Notepad++ – Set it to be the default editor for .ini and .php files (standard notepad will work too, but…)

To fix the problem, first I opened the php5.ini file by right click and choosing “View / Edit” from the dropdown in FileZilla and added the following line to the end:

memory_limit = 256M ;

(Note: If you aren’t running php5, upgrade or get a new host that has it)

Then, add the following code directly above “// ** MySQL settings – You can get…” in your wp-config.php file using the same method in FileZilla. (also in root)

/** Memory Fix */
define('WP_MEMORY_LIMIT', '256M');

Make sure you save both of these files back up to the server.

IMPORTANT: SAVE / BACKUP COPIES OF YOUR FILES IN CASE SOMETHING “BREAKS”.

Last, but certainly not least, if the change doesn’t take effect immediately, go to this page and follow the steps for your hosting OS.

*** The reason I like to utilize, and recommend the FileZilla Combo is that it provides a quick way to make edits, and back them out in a hurry using the undo buttons if they don’t work. Simply undo the changes, save the file and reload it back up to the server with FileZilla. DO NOT CLOSE THE OPEN FILES IN NOTEPAD++ UNTIL YOU ARE 100% SURE THAT THE CHANGES YOU MADE WILL BE EFFECTIVE AND WON”T CAUSE ANY ISSUES.

ok tried that and I already have 256M still getting memory issues

any updates on this issue ?

i am getting the same problem when trying to update all my 3.1 sites to 3.2.1 on the same server they were are all working perfectly on.

have set php memory limit to 256mb and am using php 5.3.8 and mysql 5.1

I just had the same issue here. I was already on 3.2.1.
Is this a real wordpress bug? Or is it related to my hosting service? I’m contacting them now, but…

Hi,

Just tried to upload photos into media and got…

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 19648 bytes) in /home/finskisc/public_html/wp-includes/media.php on line 254

We only upgraded last night and now error messges.

Being new to wordpress what should we do?

Ok,
Having the same issue, it is a hosting issue, If your database + plugins are larger than what your hosting provider can provide there is nothing they or you can do. I have rebuilt my website to get ride of all the junk in the database and I only use the plug ins that are necessary. But typical memory that hosting providers give is 30mb. I am with 1and1 and they just upgraded to 60 mb memory so that is how I got it fixed.