This question gets asked a lot… (the search function at the top of the page is great for looking up quick answers to problems like this)
—
1. If you have access to your PHP.ini file, change the line in PHP.ini
If your line shows 32M try 64M:
memory_limit = 64M ; Maximum amount of memory a script may consume (64MB)
2. If you don’t have access to PHP.ini try adding this to an .htaccess file:
php_value memory_limit 64M
3. Try adding this line to your wp-config.php file:
Increasing memory allocated to PHP
define(‘WP_MEMORY_LIMIT’, ’64M’);
4. Talk to your host.
mmm, I think the real issue here is your permalink structure. you’re likely using verbose rules. those are turned on when your permalink structure starts with postname or category. this then causes WP to store a huge array in the options table, and unserializing it can exhaust the available memory on large sites.
use something that starts with a date or year instead.
But the wordpress code now says:
%postname%
A sanitized version of the title of the post (post slug field on Edit Post/Page panel). So “This Is A Great Post!” becomes this-is-a-great-post in the URI (see Using only %postname%). Starting Permalinks with %postname% is strongly not recommended for performance reasons.. *** Note – this has been changed and is ok to do since ver. 2.0
Is it still not advisable to do this? Any idea how to correct someone who is far down this hole?
Is it still not advisable to do this? Any idea how to correct someone who is far down this hole?
This has been debated to death. It would be nice to see a DEV update this page once and for all about whether this works or not.
I have a couple of sites using it with only 16M php memory…granted they aren’t high volume.
