Wordpress 2.2 Fatal Error - Allowed Memory Size Failure

Just thought everyone out there using Wordpress might want to know the research I found on “memory allotment failure.”  Saved my, butt because I kept getting all kinds of error and weird screw ups because my site has gotten so large that I couldn’t auto create a sitemap any longer due to over 8mb’s of memory being used to create my sitemap.

 Also had to due with the use of some other pluggins and tools I’ve got working for me on the backend.

Just some of the errors people were getting…

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 122880 bytes) in /DISK3/WWW/petrtur******/web/wp-admin/admin-functions.php on line 518

 Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 122880 bytes) in /DISK4/WWW/lightimagin********/www/blog/wp-admin/admin-functions.php on line 518

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 4608 bytes) in /home/*******/public_html/wp-admin/admin-functions.php on line 2242

Now for what you’re actually wanting to know…  What is the fix?

  1. Log on to your cpanel. (Or if you’re savvy enough just use your FTP program thats actually what I did.  Just use
  2. Go to file manager and it will opened in new windows or tab.
  3. Go to public_html directory and find .htaccess file. If that file doesn’t exist, create a new one and name it as .htaccess.(public_html is just the cpanel default, you might have a different file which holds all your html documents.  So just fin
  4. Edit .htaccess file and put this command “php_value memory_limit 32000000”(no quotes).
  5. Save and try to recreate the error.  For me that was just publishing a post.

——-

Sources used in my quest…

http://wordpress.org/support/topic/122084?replies=3

http://wordpress.org/support/topic/104365?replies=8

http://onlinemarketerz.com/?p=565

[?]
Share This

One Response to “Wordpress 2.2 Fatal Error - Allowed Memory Size Failure”

  1. Genius!

Leave a Reply

Close
E-mail It
ss_blog_claim=5b692e1bffe08d3fc390ab7bdcc99158 ss_blog_claim=5b692e1bffe08d3fc390ab7bdcc99158