I have a situation that is driving me nuts. History: Hosted with Go Daddy, all was well with the site until....... I upgraded from 6.14 to 6.16. At first I uploaded 6.16 thru fetch. Problems. Then I used Go Daddy to upgrade to 6.16. All seemed fine. 6.16 created its new database. I exported my database from 6.14, imported it to 6.16 and the whole thing breaks. I used backup/migrqate and php. Before I import the database the site works albeit not the way I have it set up. I'm no pro so if I am incorrect pardon me. My thought is that having 6.16 running on the live site, then importing the database that was based on 6.14 could somehow compromise 6.16? If this is true, or even if not, what should I do? I have run out of thoughts and patience. Thanks in advance.
Comments
You shouldn't create a new
You shouldn't create a new database when you update anything, just overwrite the core files, then run update.php
http://drupal.org/upgrade/tutorial-introduction
login to your site then go to yoursite/update.php and follow directions. This will update your database to be compatible with the new version of Drupal. report back.
Also, you might want to check out www.drupalgardens.com - A hosted solution like this would remove all these server-side problems.
I've got a site hosted on
I've got a site hosted on godaddy so I think I have an idea of what happened here. I'm thinking you're missing a bunch of modules on the new installation. Easiest way to upgrade a site currently hosted on godaddy: move to a different provider.
BTW if you're interested in checking out Drupal Gardens I picked up some beta trial codes from the Acquia booth at DrupalCon.