• I’m doing some work for a client who runs a wordpress driven site. He wants a few updates, some are fairly complicated and because of that, I’m attempting to set up an instance of his current site on my test/dev server.

    Below are the steps that I’ve taken to create the new instance on my server:

    • Install WP 3.0.1
    • Drop all tables created from fresh install
    • Import clients current database

    NOTE: Both instances run 3.0.1

    The problem: when i import his current database, WP reverts back to the install sequence and basically forces me to reinstall. Why?

    I feel like I’m missing something easy. I’ve done this dozens of times w/o issue but for the life of me – I can’t get this figured out.

    Thanks!!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Import the database and in phpmyadmin change the url in the wp_options table to your local/test server. Load the site click the install and it should report that it’s all ready been done and then you should be able to access the site.

    Thread Starter Meyerbytes

    (@meyerbytes)

    Thanks threestyler! Turns out that the tables from the live database I imported to my dev environment had custom prefixes…didn’t even notice. Instead of the standard ‘wp_’ prefix, they looked more like ‘wp_xxx_xxxxx_xxx_’.

    Sooooo – each time I went thru the install sequence, wordpress looked for tables beginning with ‘wp_’, couldn’t find any and freshly installed wordpress with the default ‘wp_’ tables ontop of the already existing tables w/custom prefixes.

    Not one of my brightest moments 🙂

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Importing new database causes reinstall’ is closed to new replies.