How do I keep current database with fresh install on production site?

By HelpDrupalHelpMe on 27 Feb 2008 at 06:24 UTC

This is easier than it sounds, trust me!

Ok so I have my test site complete and I want to go to production site / live site. I want to keep the current database from my test site BUT I want a fresh clean install of Drupal on the production site/server.

When I run the install I get an error telling me that "Drupal is alredy installed" because the database from the testsite.

I actually bypassed this and got it to work BUT something is nagging me at the back of my mind telling me "I didn't so it the right way"

SO THE QUESTION IS: How can I import my test site database while still having a fresh install of drupal on the production site? What is the proper way?

Comments

Um. I do understand your

dman commented 27 February 2008 at 07:27

Um.
I do understand your problem, but your problem is that your test site that you want to import is what has the cruft you want to avoid :-O

Uploading a fresh files distro and pointing it at your old DB is quite OK. That's effectively the process you go through when upgrading.
Youll need to go through the same upgrade steps (disable add-on modules) if you want to be careful, but It's not to painful to create a really broken site then add back the modules you forgot one-by-one ... if you are happy to mess around in the dark for a few hours.

Anyway, the short answer - if you've not got too many add-ons, is : do not run install - Point it at your old db and run upgrade.
That will therefore start to use all your old settings. Probably some of which you want to leave behind, but there's no way of telling the difference unless you choose each db table by hand - and you don't want to do that.

Sorry.

.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/

_{.dan. is the New Zealand Drupal Developer working on Government Web Standards}