carlostapi

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.

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

oka. thanks,

you know other way to increase de memory in WP 3.2.1 I try phpini, httaccess, and wpadmin. but dont work…

you know if exist other page in admin o includes that need increase the memory too?

Look this I can put TCP Memory plugin and look.

Memory Usage Overview
Usage Sample: 14.11MB (10%)
Peak Usage: 14.23MB (10%)
All-Time: 14.23MB on 7/15/11 @ 7:27 pm (shutdown)
Load Averages: 0.09 0.12 0.14
WP Memory Limit: 128M
PHP Memory Limit: 139M

I have a memory, but the INCOMING LINK said: Fatal error: Out of memory (allocated 14680064) (tried to allocate 388172 bytes) in /home/webandho/public_html/wp-includes/class-feed.php on line 4

And

plugin said Fatal error: Out of memory (allocated 14680064) (tried to allocate 388172 bytes) in /home/webandho/public_html/wp-includes/class-feed.php on line 4

both in the dashboard… I Reload WP 3.2.1 10 times over the server…

And the Wp Team, dont said anything???

Why put online WP 3.2.1 if dont fixed the tipical problem out of memory… I think wp.config came pre-set with memory in 128M and put php.ini