Upgrading Drupal

oh no! I've broken my drupal (on wamp) trying to downgrade from 6.4 to 5.10. Now it won't work as 6 or 5. "The more I fix it - the worse it gets :-(("

I thought I was covered - having monthly backups and indeed one called 'manualpreupgradebackup'.

'manualpreupgradebackup' is a folder with two objects in it
1) a folder called 'copy of drupal', and
2) a file called 'copyofdrupaldatabase.sql'

My 'restore' procedure is from 4.6 and I don't think it was really written for this major an upgrade.

To recover I
- copy folder 'copy of drupal' (from 1 above) to C:\www\webapps\
- rename the 'drupal' folder already there to 'drupal6', rename the 'copy of drupal' folder to 'drupal'
- copy file 'copyofdrupaldatabase.sql' (from 2 above) to C:\www\mysql5\bin\
- open a command-prompt and navigate to C:\www\mysql5\bin\
- enter the command 'mysql -u root -p rootpw drupal < copyofdrupaldatabase.sql' (with the real root password)

and voila ... a big pink box of select statement errors

user warning: Table 'drupal.file_revisions' doesn't exist query: SELECT * FROM files f INNER JOIN file_revisions r ON f.fid = r.fid WHERE r.vid = 66 ORDER BY f.fid in C:\www\webapps\drupal\includes\database.mysql.inc on line 172.

I am having trouble with the administer panel of Drupal. It seems to think that the Drupal Version is still 6.3, even though 6.4 was successfully installed. I viewed the changelog and it shows 6.4 being the latest install, therefore Im not sure what the issue is. I went around the forums but didnt find anyone with this this issue, was wondering if someone could help me find out how and why this is happening. Thanks In Advance!

Alvin C.

This one is a bit of a mess. Apologies in advance.

I had a 5.something install running fine on a shared server. Said server was upgraded right at a time when the people needed to keep me in the loop were all taking finals then leaving campus for 3 months.

The upgrade moved to mySQL 5, which, among other things, broke the original Drupal. (That is my assumption, at least!) All the files are in the right place, and now that I have access again, I can confirm that the db is still intact.

Federal Debt Relief System Used on drupal I have a problem when I want to upgrade drupal 5.x in 7.x
it give me a problem something Federal Debt Relief System error.

I have a Drupal 6.4 installation that is configured for multisite. I've incorporated a few Drupal sites into it as well as rolling in a few WordPress sites. This multisite install currently has about a dozen domains running off of it.

So I decided to migrate my primary Drupal install into this - this is my site that I've maintained since 1997 and has gone through one CMS to another before settling on Drupal years ago. It also has the most tricks and modules installed into it. I've upgraded it to 5.10 without any issues.

I have been copying the database ("drupal_q to drupal_qdp") and using the new database to perform the upgrade on as a test site. I'm glad I did that. Each time I try to upgrade this site, I get the following error:

Fatal error: Unsupported operand types in /httpdocs/drupal-6.4/includes/common.inc on line 1445

Ok. Drupal 6 is probably the best thing since bread came sliced. Views 2, the new and improved CCK, and the updater—it’s like updating your anti virus—has made life so much easier. Updating Web application frameworks has never been easier.

This updater alone is incentive enough to upgrade your Drupal 4.x and 5.x installations to Drupal 6.x. Unfortunate it is then that this moat to be crossed is filled with non-upgraded module crocodiles and inexplicable PHP error sharks.

There are two approaches to converting a Drupal 5.x site to 6.x:
1. Upgrading: For this, all contrib. modules installed in your 5.x better be ported to 6.x, and also pray that Watchdog has encountered no life-threatening PHP errors. That periodic cron runs, database updates, & zilch-modification of core modules were a must go without saying.
2. Migration: Setup a crisp, clean Drupal 6.x site, and painstakingly port all data from your 5.x behemoth to your 6.x kiddo. Migration can be performed either manually (pray, lord, pray if your site has more than 500 nodes) or through scripts.

Although approach 1, if it works without spewing any errors, is enough to incite a hallelujah from even the most ardent of the non-believers, we all know how rare it is. And the pre-requisites to it are just too many and too hard to fulfill.