Upgrading Drupal

I upgraded my system from 6.12 to 6.20. I accidentally ended up with two directories of the drupal 6.20 core modules:

mysite/modules (the correct location)
mysite/sites/all/modules/drupal-6.20 (duplicated modules)

The problem is, I cannot simply delete the drupal-6.20 folder. The system is using those modules instead of the ones in the normal modules directory; I assume it found them later or something. Deleting the drupal-6.20 folder causes all sorts of error messages.

Hey out there!
Did anybody else experience the following after moving to 6.22: All of our SEO rankings have dropped, some by 40 percent, some right off the top 500. For instance, we were ranked 15th on Google for 'fallout zone' and then we dropped below 500 for that keyword combo...starting the next day after the upgrade. We did pop briefly in the high teens again for a couple days and now back off the top 500. We aren't doing anything different, just the upgrade. This is true for ALL keywords that we track...

I'm relatively new to Drupal. I started with D6 so I've never gone through an upgrade. I haven't yet attempted to upgrade because I wanted to make sure I knew what to do after I get there.

Right now I have a customized installation profile for D7, I've backed up my database, and I'm ready to upgrade (I think.)

This is the process as I understand. Disable all of my modules. Run the update to current 6.X. Then it will automatically list D7 on the update page? If yes, how to I add my custom install profile to the update page?

Once I get D7 going, do I just identify my current db and it will automatically migrate all of the information within into D7? I.e. all my blog entries will now by on the new install? Or do I have to set the db fresh with D7 and then migrate the tables manually into the fresh db.

Have you found it better to try and manually update the db or to use a fresh db and use modules like Migrate to manually migrate content and users over to the new install?

I looked through the docs on upgrading but either I'm missing something or I'm too stupid to understand what it's saying. I seem to be missing the part that comes after you upgrade and getting your backups into your new db (if there even is a new db.)

I did the update from ver 6.21 to 6.22 as instructed in the Administrative Guide: http://drupal.org/node/390448.

Turn site off-line; disable contributed modules; upload the new version, except keep your /sites folder; run update.php; enable the contributed modules; run update.php again; return site to on-line setting.

All the Blocks, except for the User Log In, were disabled. This has happened previously when I did other Drupal version 6.x updates. Is this the expected results after an update?

Ashford

I'm just sharing this... it's a non-problem for me because I'm way far fed up with Drupal today, but it may be useful info to someone.

I upgraded, per the orders of the pink box, from Drupal v7.0 (IIRC) to 7.2. I installed Drupal via GoDaddy, so must update via GoDaddy. GoDaddy reported no problems. A couple hours later, I clicked on "Modules" and discovered that every Module was disabled.

I am looking at a site which is currently running 5.19 and we would like to bring it to 6.x or 7.x. Before diving in, I would like to research module availability and status to see whether 7.x is a reasonable target and whether or not there were any issues about modules we are using that have fallen by the way side.