Bad Move, change prefix in wp-config, lost ALL

  • Yes, I tried and failed. What to do now?
    –
    Objective: move from my working install to a multi-blog system.

    Method: chane the prefix from wp_ to wpEQI_ in wp-config.php. Export the DB as an SQL file. Text search and replace on the SQL file, changing the prefix on all the tables. Reimport the new data. Viola!

    Result: WordPress decided that I have a new install, and init’d all the tables, with the riht prefix. And my sidebar and theme work are gone. (yes, I have a backup locally) I et the generic Hello World blue blog. I even tried AGAIN importin the tables. No way.
    And, running the admin install says “looks like you already installed wordpress”. ughh

    What to do?
    I could probably et back to where I was, but really, I do want to have a new prefix, and install a new blog in another directory.

    pointers appreciated. thanks
    -Brian

Viewing 6 replies - 1 through 6 (of 6 total)

  • Have you got phpMyAdmin?

    If so load it up, delete the tables WordPress created and rename all the tables to have the new prefix.. If you don’t you may either have to install phpMyAdmin or use the mysql cli tool (if you have a shell)

    Thread Starter ewasteblogger

    (@ewasteblogger)

    yes, I have a workin phpMyAdmin, part of why I was brave enough to try this reckless move.

    In the post, I mention that I tried re-uploadin the tables, and that did not seem to take. I will look again. Still appreciating advice here!

    Think I may have misread your post first time over.

    Probably best to start over from your backup in your current situation.

    Has anything else changed (upgrading to 2.0 at the same time or anything else like that?)

    If it is just a standard prefix change, that shouldn’t be too much of a problem, as I have done that myself, just using phpMyAdmin as I mentioned above.

    Thread Starter ewasteblogger

    (@ewasteblogger)

    no upgrade involved, just the change to the prefix.

    maenwhile, I have deleted all the empty tables, and am reuploading the SQL data. thanks, I’ll be back soon…

    To be told that you haven’t got an install means that WordPress was unable to open your database and read:

    v1.5: any users defined with a level > 0
    v2.0: a siteurl in your configuration options

    I’ve seen this occur for people have wrong database names, wrong prefix names or running v1.5 code on a v2.0 database.

    Thread Starter ewasteblogger

    (@ewasteblogger)

    pardon, but the msg said ‘already installed’, not can’t install.

    BUT Praise and Glory! By DELETING all tables and REIMPORTING aain, makin sure that the LINE FEEDS were set to 0xA in the text file, I now have the WP Back Again!

    Panic is subsiding. I will now forge on to the second WP install usin another prefix. thanks all

    https://ewasteInsights.info

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Bad Move, change prefix in wp-config, lost ALL’ is closed to new replies.