WP 3.0 – Fatal error: Allowed memory size of 33554432 bytes exhausted . . .

Posted in WordPress - 18 June 2010

Today WordPress.org released the new version of the WP – WP 3.0. The new version is a very impressive update of the cms. But soon after upgrading from my 2.9.x to 3.0 version of wordpress, i tried to make a post in the admin panel and upon publishing it i got this error on wordpress 3.0:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 491520 bytes) in /home/mukhbirc/public_html/addon/nabtron/technab/wp-content/themes/thesis_17/lib/classes/options_site.php on line 851

Well this error is nothing new for many of us. To fix this error, simply follow this:

1. Goto your wordpress root directory

Either login via ftp or use the filemanager if your web host provides you with this feature (to get a cpanel based hosting click here).

2. Edit the config file

In your wordpress 3.0 installation root folder, find the file named:

config.php

Open the file to be edited in your favorite editor

3. Add the code to file and save

Add this code to your config.php file ( type it manually if it don’t work on copy / paste )

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

after the lines :

/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8');

/** The Database Collate type. Don't change this if in doubt. */
define('DB_COLLATE', '');

Save the file and refresh your wordpress page and it should not give the error again.

If the error still appears then try changing 64M to 128M.

Let me know if error still persists.

Update: If you are still having the issue while updating your wordpress to 3.0, try deactivating all the plugins and try again (thanks to kazimir)

You might also like

107 Responses to WP 3.0 – Fatal error: Allowed memory size of 33554432 bytes exhausted . . .

← Older Comments
  1. Emmy says:
    October 16, 2011 at 1:38 am

    Didn’t work for me… and deactivating the plugin caused more errors.. :(

  2. Jae Dyer says:
    October 18, 2011 at 3:39 pm

    I am having the same issue as they are describing below. I tried everything, even the directions you mentioned here and nothing has changed. I am getting the same error. I am depritely pleading for help ASAP.

  3. Norbert says:
    October 18, 2011 at 11:05 pm

    Thanks for this article. This wars really nice and helpfull..best wishes Norbert

  4. Martin - Inverness Web Designer says:
    November 1, 2011 at 4:43 pm

    Many thanks for posting this solution, it’s taken me over half an hour of searching to resolve this issue on a client’s website and your fix has solved it.

    You posted this middle of last year and WP has evolved since, but it still works so glad I found you with an epic long-tail search!

  5. Ralf Kothe says:
    December 28, 2011 at 11:42 pm

    Thank for this advise. My page runs again.

  6. Matthias says:
    January 31, 2012 at 4:12 pm

    Hi,

    first thx for your solution, i follow your instructions, but id doesn’t work. I added also the 128 M, but not succesfully.
    define(‘DB_CHARSET’, ‘utf8′);
    define(‘DB_COLLATE’, ”);
    define(‘WP_MEMORY_LIMIT’, ’128M’);

    could you help me on?

    .mag

  7. webuser says:
    April 23, 2012 at 3:19 pm

    Great, thanks. The fix in the wp-admin that is suggested all over did not work, but yours did. Perfect

← Older Comments

Leave a Reply