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

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)

Was it helpful? How about buying me a coffee? It helps me write great content for you!

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

  1. Norbert

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

  2. Martin - Inverness Web Designer

    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!

    • Dr. Nabeel

      Glad to know it fixed the error for you

      can you tell me the keywords you used for search?

      • Martin Oxby

        Just saw your reply 7 months later :-/ I’m sorry, I didn’t subscribe by e-mail.

        I think it was just a copy and paste of the actual error, rather than just a ‘keyword or keyphrase’ :)

        • Dr. Nabeel

          ook, btw, what bought you back here again after so long ?

          • Martin Oxby

            Just checking through all of our website’s backlinks and saw this thread in the list and realised I had been rude and not replied. So I’m sorry for that.

          • Dr. Nabeel

            don’t be sorry :) its fine!

  3. Ralf Kothe

    Thank for this advise. My page runs again.

    • Dr. Nabeel

      glad to know that it worked for you Ralf

  4. Matthias

    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

    • Dr. Nabeel

      it could be due to server settings, did you try talking to your server guys about it ?

  5. webuser

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

    • Dr. Nabeel

      Glad to know that it worked for you marcus to get your wordpress error fixed . . . and sorry about late response . . . very late infact :)

Leave a Reply

Your email address will not be published. Required fields are marked *