Hello ostraining folks,
Our website (livingcitymagazine.com) is undergoing a migration process from drupal 6 to drupal 7. We are testing the modules on a test site and we want to start the migration on the production test.
Our host company offered us to create a sub domain with a copy of the site and so when we are done withe the upgrade we can switch the database and file folders.
Our question is: is it better to install a new drupal version site with a copy of the database that we are using now, then install the modules that we need for our website. Or we should just install a copy of the web site into the sub domain and proceed with the migration process.

Thank you for any advice.

Regards,
Mariana

Hi Mariana

That won't work I'm afraid as the D6 and D7 database structures are so different. You'll need to start with a brand new copy of Drupal 7, oh ... and maybe these tutorials too ...

www.ostraining.com/blog/drupal/planning-...al-6-to-7-migration/

www.ostraining.com/blog/drupal/migrate-drupal-6-to-drupal-7/

www.ostraining.com/blog/drupal/migrating...it-cck-to-d7-fields/

Thank you, Steve!
I printed the three tutorials and I am following those instructions. They are extremely useful!
I just wanted to add another question: after I run the update.php I got an error saying that:I found an articlesuggesting to drop the upload table on my database. I did it and after that I didn't get the error message anymore.
I am going to need that upload table? What is that for?

Thank you again for your prompt reply!

Regards,
Mariana :)

Hi Mariana

Sorry, backup and talk me through this a bit more.

What are you aiming to update when you run update.php here?

Hi Mariana,

The upload table stores information about files uploaded via the file upload module (and used by some other modules too). The file upload module was migrated to the core in D7.

This was necessary in D5 and D6, but I'm unsure if it's necessary in D7. I'll see if I cn verify it. So far I haven't found any reference to it.

Ed

Hi Steve, the message appeared after I upgraded the drupal 7 core and run the update.php.

Hi Mariana,

I read the article and did some other research.

The only cause reported for this that I can find is case sensitivity in the database table. There are entries with the same name and different cases so they violate the uniqueness rules in mysql.

If you deleted the table, then ran update.php it might have re-installed the table for you, in which case you'll be able to operate normally, although I don't know the effect it will have on existing data. You could check to see if that table was repaired.

One suggestion is to look for entries with the same name and rename them in the D6 database and before starting the upgrade.

This article has a thorough discussion and several patches that might solve this problem. drupal.org/node/966210

This deals with a related problem, and may help track it down.
drupal.org/node/1237252

Look at these and let us know if they relate to the problem you're having.

Ed

Hi Ed,
thank you for taking the time to go through all this info. I read the two posts in drupal.org but don't see them related to my issue. In checked the database after I run update.php and the upload table wasn't re-installed it. I am upgrading some modules now without problems. I think I can live without the upload table. What do you think?

Thanks again!

Mariana :)

Yes, if it's working you do not need to fix it :) I was looking for some confirmation that eliminating the tables wouldn't hurt, but I could find no references to it at all.

This must not happen very often or the fix you found satisfies everyone, so there's not a lot of reference to it.

Keep at it. If you find out that it causes problems, let us know and we'll start up some research on it again.

Cheers,

Ed