WordPress.org

31. MichaelH
    moderator
    Posted 5 months ago #

    Restoring_Your_Database_From_Backup

32. war59312
    Member
    Posted 5 months ago #

    Even after applying the fixed file I still have to now use max memory usage of 64M when 32M was just fine before upgrading to 2.8.

33. mcbalz
    Member
    Posted 5 months ago #

    Michael, I followed the advice at the link you provided, but it just duplicated all of the database categories, now titled wp_2comments, etc... when I run the new installation it doesn't find any of the old posts.

    In other words, the instructions there allowed me to import the 10 old WP SQL tables into my new database, as ten ADDITIONAL tables. But how can I get WP to recognize them?

34. MichaelH
    moderator
    Posted 5 months ago #

    mcbalz,

    If you are moving to a new site, but just want your old tables, you should be DROPping the new tables then do the SQL import.

    With that said, if you are sure you want to merge the two databases might restore the old tables into their own database, access those tables as a normal WordPress site, then do Tools->Export.

    Then with the new tables blog do Tools->Import->WordPress.

35. mcbalz
    Member
    Posted 5 months ago #

    Michael,

    I am (or rather, have already) moved to a new site. I was forced to do that. At present, it is a totally blank WP install, with no custom theme and only one post... "Hello World!"

    There's no way, it seems, for me to access the old tables as a normal WordPress site... they are a .sql file. That is the only form in which they exist.

    But if I delete the new tables in the new database, then import the .sql file containing the old tables, the site doesn't work. A blank screen comes up.

    What do you make of this?

    MCB

36. mcbalz
    Member
    Posted 5 months ago #

    I should clarify my last post... my new WP install is now dead because I deleted the old tables and imported the new ones in their place. Strangely, they did not import with the proper names (they added a "2" in front of the names, i.e. wp_2comments instead of wp_comments). I renamed the tables to wp_comments, etc.

    But a completely blank browser window is all I get. WordPress ceases to function entirely.

    Also, there doesn't seem to be any way for me to get it back, short of recreating the database entirely from scratch, and reinstalling a freshly unpacked WP from the .zip. In other words, starting really from the beginning again. Which leaves me where I was.

37. MichaelH
    moderator
    Posted 5 months ago #

    But if I delete the new tables in the new database, then import the .sql file containing the old tables, the site doesn't work. A blank screen comes up.

    The new domain is the same as the old domain?
    The $table_prefix is the same?
    WordPress is installed in the SAME folder (e.g. web-root) at the new host as it was at the old host?

38. mcbalz
    Member
    Posted 5 months ago #

    Michael, I really appreciate your patience and persistence here. You are an IT god.

    The answers to your questions are:
    yes
    NO (I didn't realize this before, but you caused me to check)
    yes

    So, in the new, working, but empty WP install, I corrected the $table_prefix in the wp-config.php file. Then I deleted all the tables in the new, working but otherwise empty database. And I imported all the old tables, which had the different table prefixes.

    Now I am going to test the thing... drumroll please...

    No, I am so sorry... it doesn't work. A blank screen comes up, that's all. Why is this happening?

    *** later ***

    I finally did make this work... by tinkering with the existing tables in the new install. Here's how I did it.

    First, I once again deleted all the tables inside my database, and ran a fresh install on the WP 2.8. What I learned from doing this (3 times before I got everything right) is that the "5-minute install" process is designed to take an empty database and set it up with the appropriate table structure. (Therefore, If you first delete the tables in your MySQL database and then try to open up your blog, it will effectively reinstall itself; like I said I did this about three times).

    Trying to import the old tables into the new ones did not work. There were errors in the import. The inner structure of the tables did not match. It turns out that the backed up tables from my old blog were not created by a WP 2.8 install. What version was out in the days immediately prior to the official release? That was what I used.

    Anyway, the result was that the WP_links, and the WP_Options table were both incompatible with the new release. But what I learned in the process was that the data had partially imported. I got working comments, but not working posts. It was importing the tables alphabetically and quitting (exiting the process) when something incompatible came up.

    So what I did was I took a copy of the MySQL database dump file from the previous version and, using a text editor, deleted all the data relating to the options, links, and users tables (4 tables) leaving the relevant tables only for comments, posts, and terms (6 tables).

    I then deleted all the comments, posts, and terms related tables on the new install. Then imported the copy.

    BINGO. My blog is up and running. Time to customize.

    http://eschata.apocryphum.com/

39. NancyLaMont
    Member
    Posted 5 months ago #

    Hi, I see these posts are related to my problem except I got the following error not from upgrading. I already had 2.8 and was just adding plugins:

    Manage Plugins
    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /home2/beeroyal/public_html/wp-includes/kses.php(401) : runtime-created function on line 1

    I cannot get inot my plugins to delete or deactivate any. What can I do?
    Thanks,

40. MichaelH
    moderator
    Posted 5 months ago #

    @NancyLaMont
    How to deactivate all plugins when not able to access the administrative menus?

41. praskuma
    Member
    Posted 5 months ago #

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

    to config.php as suggested by gestroud
    solved my problem.

42. Smashingkris
    Member
    Posted 5 months ago #

    I had the same errors. finally got it fixed. editing config.php and adding php.ini didnt work for me.
    try this link http://tinyurl.com/ntml96 .....i made a post on how i made it work. hope that helps :D

43. katendarcy
    Member
    Posted 4 months ago #

    @elking10: I was actually upgrading a site for a client, and got this error. I had just upgraded another blog to 2.8, so I was a little puzzled. I saw on the sidebar that they had several plugins that needed updates. I went through one by one until I got to TDO miniforms... and I got the same error I got originally while trying to upgrade to version 2.8.1.: memory exhausted. I still poked around with the memory fixes for a while, but when I came across your comment, I realized the plugin was the issue. Deactivated it, upgraded WP, and re-activated it. It worked! :) Now I just have to figure out how to update TDO MiniForms as it's still exhausting the memory...

44. Jhon_alkorn
    Member
    Posted 4 months ago #

    @ MichaelH, thanks for the "restoring your database from backup" link :)

    [signature moderated Please read the Forum Rules]

45. CorbanRaun
    Member
    Posted 4 months ago #

    You could also add this line to your wp-config.php

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

    This way you won't have to constantly make the fix again whenever you upgrade WordPress.

    This worked for ME Thanks G!!!!

46. ts.ts
    Member
    Posted 4 months ago #

    For me the solution was to deactivate the plugin

    Simple Tags

    After that I recived no more error messages.

47. NienOnline
    Member
    Posted 4 months ago #

    Finally got around to contacting my host. They moved me to another server with a higher memory limit.

    Everything is working again!

48. josephilipraja
    Member
    Posted 4 months ago #

    Well I had the same problem too... When I tried to upgrade from Wordpress 2.8 to 2.8.2 I got a Fatal Error saying allowed memory size exhausted..

    I just tried Deactivating the active plugins and clicked the Automatic Upgrade mode.. It all worked fine... :)

49. dashmoo
    Member
    Posted 3 months ago #

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

    is what worked for me. Thank you :)

    Miss Louise

50. brechtp
    Member
    Posted 3 months ago #

    I was having this error on the auto upgrade to 2.8.4
    I set the wp-config to 64M as described above and additionally the includes/cache.php and my problem was solved

    very easy thanks to all

51. emda82
    Member
    Posted 3 months ago #

    I've found upgrading my WP quite difficult due to the fact that my Host is cheap and therefore less memory than I would like. Though I found a workaround that I wanted to share.

    1. Install PHP on your own computer and a web server like Apache. (if you don't already have one.
    2. Unpack the Wordpress upgrade to your "local" root dir or wherever your web server is pointing.
    3. Copy your wp_config.php file to your local server with loads of memory allocated to PHP.

    Presto, the upgrade runs on your local computer but does all the DB, upgrades and such on your host-server.

    Happy word-pressing..

    *Should add a warning that I give no guarantees this will work 100% though it did for me.

52. alanbliss
    Member
    Posted 2 months ago #

    thanks gestroud, worked a treat

53. adelio.fioritto
    Member
    Posted 1 month ago #

    I solved my problem by these steps:
    1. in wp_config.php adding: define('WP_MEMORY_LIMIT', '64M');
    2. in wp_include/cache.php adding: ini_set('memory_limit','64M');
    3. creating php.ini local file adding: memory_limit = 64M

54. se7en111
    Member
    Posted 1 month ago #

    thank you for that tip adelio.fioritto
    I have done 1 and 3 without any changes.

    2. in wp_include/cache.php adding: ini_set('memory_limit','64M');

    that was the missing code.

    everything works fine now thanks.

55. sullivanka
    Member
    Posted 1 month ago #

    I had the same issue so called my host. We first went to file manager--> and in the public_html found the php.ini file and right clicked on it and chose edit code. code window opened and used the keyboard combo Control F to open a search field where I typed in "Memory". Brought to code line where I was able to change memory limit from 32 M to 128 Meg (by the way, this is arbitrary, and based on whatever you want to allow scripts to use). Saved the changes and fixed.

56. adhyaru
    Member
    Posted 1 month ago #

    had similar problem

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2354671 bytes) in /public_html/wp-includes/http.php on line 1331

    I have deactivated some of my plugins like Cforms, nexgen gallery and popularity contest etc and then upgraded....

    it solved the prob.

    Again after upgradation, all plugins activated successfully...

57. mikejkim
    Member
    Posted 3 weeks ago #

    @gestroud Your tip worked perfectly. Thank you!!

58. jclayc
    Member
    Posted 3 weeks ago #

    Deactivating all plugins and then upgrading fixed the error for me...

59. virg
    Member
    Posted 2 weeks ago #

    On some servers, editing the wp-config.php, doesn't fix the issue. You need to install a "php.ini" file and increase within it, the post_max_size = 32 to 64 or higher. Here are the instructions for this from my host:

    Step 1- Login into your cPanel.
    Step 2- Under the Software/Services category, click on the PHP Config icon.
    Step 3- In this screen, there is a section called “Install Default php.ini”. Under that section, please check mark the "IonCube" and the "SourceGuardian" check boxes (Many commercial php scripts need these turned on - if you think your script may not require the IonCube or SourceGuardian packages, it is okay to not check mark the boxes - but it will not hurt anything to check mark both boxes.).
    Step 4- Under the same section, click the "INSTALL PHP.INI MASTER FILE" button.
    Step 5- You have just successfully installed the "php.ini.default" file . But the next step is to rename it from "php.ini.default" to just "php.ini" to make it active. You can do the Rename in the File Manager screens. Under the Files category in your cPanel, please click on the File Manager icon.
    Step 6- When you click on the File Manager icon, you should get a popup dialog titled "File Manager Directory Selection". (If you do not see the popup dialog, then you need to click on the link at the bottom of your cPanel called "reset all interface settings" - and then Refresh your cPanel and click on the File Manager icon again.) In the popup dialog screen, click the "Web Root (public_html/www)" and the "Show Hidden Files (dotfiles)." choices. Finally please click the "Go" button.
    Step 7- If you already have a "php.ini", I would recommend that you Rename the file to "php.iniOld" in case you need ever need it.
    Step 8- Find the file that you just installed called "php.ini.default", Right-Click the file and choose the Rename option.
    Step 9- A new popup dialog called Rename should appear. Please start pressing your Backspace on your keyboard and you will start to see the letters disappear. Keep removing the letters until you see only "php.ini", and then click the Rename File button.
    Step 10- Your php.ini file is now active and fully functional !! Additionally, some users need to make adjustments to this file. To edit the file, you just Righ-Click the php.ini file and choose the Edit option, and then change the value like these examples show:
    a. To increase your memory for your php pages: memory_limit = 2M ---> memory_limit = 100M
    or
    b. To turn on your Register Globals: register_globals = Off ---> register_globals = On (We don't recommend that you change this flag unless you know what you are doing.)
    or
    c. To increase the maximum file size for uploading (there are two flags that you have to change):
    post_max_size = 2M ---> post_max_size = 100M
    upload_max_filesize = 2M ---> upload_max_filesize = 100M
    d. To turn on PDO, add this line of code to your php.ini file:
    extension=pdo_mysql.so
    extension=pdo.so
    extension=pdo_sqlite.so
    extension=sqlite.so
    Step 11- Important: The php.ini file is generally directory specific. If you have "PHP5 (Single php.ini)" or "PHP5 (FastCGI)" selected in your Php Config screen, then you should not need to do anything else. If you do NOT have either of those selected, then you may need to copy the php.ini file into all of the subfolders inside your public_html directory. This may be dozens and dozens of subfolders that you have to copy the file into. Also, sometimes it can take between 15-30 minutes before the system recognizes the php.ini file or any changes that you have made in the file.

    I just followed part a. and it fixed the problem. My Wordpress site seems to work fine now!

60. tomturnerjr
    Member
    Posted 2 weeks ago #

    @gestroud Thank you for your tip (provided below) It worked perfectly for me. Thanks!

    @gestroud recommended adding "...this line to your wp-config.php
    define('WP_MEMORY_LIMIT', '64M');
    This way you won't have to constantly make the fix again whenever you upgrade WordPress."

Reply »

You must log in to post.