By Chichee on

Argh...boy do I feel dumb.

Has anyone else done this but me?

I just successfully upgraded to CiviCRM 1.6 and then carefully (I thought) stepped through the process of upgrading Drupal 4.7 to 5.0. Somewhere along the way, I guess when I did the update.php, I didn't give the correct database name/table prefix and now my old tables are sitting there unchanged and I have a bunch of new tables from the 5.0 update.

Is there any way to remedy this besides restoring from backup and starting again?

My old tables all had a prefix of prod_ but the new tables have no prefix so Drupal 5.0 thinks I'm running a new site....what to do, what to do?

Thank you for any help!

⋅ Categories: Drupal 5.x

Comments

vm’s picture

vm commented

seems to me you should be able to delete all the new tables that should allow the drupal 5 installtion to run again.

Chichee’s picture

Chichee commented

I'll check and see if it works and report back here with the results.

Thanks for taking the time to post something to try. I'm crossing my fingers.

Chichee’s picture

Chichee commented

Closed.