Fatal error: allowed memory size…

Hi

You can also do two things,

1.) .htaccess file in the root directory of WordPress. Add the following;

php_value memory_limit 64M

2.) if you have access to modify the php.ini look for the following line;

memory_limit: 8M

change to

memory_limit: 64M

Then restart your apache by;

service httpd restart (on CentOS)
/etc/init.d/httpd restart (on Ubuntu)

Hope that helps, let us know.

Cheers!

Hi there,

Just have been finding a solution: had the same problem here.
After installing plugin wp-property my wp site had gone loose; dashboard lost, tried a lot, nothing worked.

What DID work was this: I just renamed the map of the ‘bad’ plugin, that caused the trouble. And there it was, back again. My dashboard…

Now have to find out about all the different places where you can tell Apache to assign more memory to php…. wich is the right one?

Anyone…? Please help.

Hi

If you have php.ini access ability, I would go in there and change the defaults to allow more memory.

??

Hi Kenton – thanks for your suggestions. Unfortunately I don’t have access to my php.ini file – so I’ve sent a mail to my web-host to get them to change it for me.

About your other suggestion: my .htaccess file looks like this –

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

As I’m a bit of a novice at these things, can you tell me exactly where I should paste your suggested line of : php_value memory_limit 64M ?

Thanks,

Kieron

Hi Kieron,

You can just put it at the very beginning of the .htaccess file, so like this;

php_value memory_limit 64M

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Some host don’t allow such things, which is a good thing you contacted them and hopefully they will change things for you. Depends who you host with, normally a shared hosting offering more then hosting for WordPress wouldn’t have things tweaked in a way for WordPress performance and stability, however some do agree and change things to accommodate.

Let me know how it goes.

Artur B.

Thanks Artur B.

I’ve just tried that, and it immediately caused a problem, meaning the whole site was inaccessible – I got this:

“Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at popeyethewelder.com Port 80

Hi

You going to have to deal through your provider on that, Im sorry.

Artur

This seems to have been fixed now. I don’t know which single factor did the trick, but these were the steps taken:

1. Adding

define(‘WP_MEMORY_LIMIT’, ’64M’);

to my wp-settings.php and wp-config.php files

2. Deactivating my google maps and flickr press plugins

3. Getting my webhost to increase the memory allowance in the php.ini file to 64M