Upgrading Drupal

Im sure this is a frequently asked question, but I cant seem to find anything. I have a site with over 1600 public files that SHOULD be perfect. Some of them are uploaded with upload.module and some are uploaded via imce. Im wondering if anyone has aproached this in the past, and what you did. I *could* attempt this manually in the files and file_revisions tables, but before I go hacking away, I'd like to hear from the audience.

Thanks
--lee

I upgraded last night from 4.7 to 5.1. Upon completion of the upgrade, I lost all of my headers. Logo, text, the works. I updated the themes to see if that fixed it, to no avail.

Any help appreciated.

Tim Sheets
Hobx.com

How can I tell what version of Drupal I am running (installed 18 months ago)?

Hi,
i have just upgraded drupal 4.7 to 5.1 all went fine
after the upgrade i made two more changes
1. changed time&date of the server
2. installed a security patch for php 5.2.1 from opensuse repository with Yast
running on openSuSe 10.2 x86_64

on checking the apache2 error log i get this on every hit to the server:

I hope this is the right place to post this.

I maintain a moderately-sized Drupal-based site that currently uses Drupal 4.7 as its base. There have been some minor modifications to its core made, and it has a number of modules that we have custom-created for it. We use CVS to manage it, with a branch containing the unmodified Drupal 4.7 code (not including 3rd party modules) which is merged into the trunk periodically (as described here: http://drupal.org/node/5123). We'd like to upgrade to Drupal 5 (and hopefully make fewer modifications to Core while we're at it), but since we've never done this before, I'm not sure what the best strategy would be.

Here's currently what I had in mind:

1. Start fresh with a new repository (I'm not a CVS guru, so the interaction between the "vendor branch" and trunk is a little on the 'magical' side to me, and there were a lot of changes to the directory structure in 5.x anyway), using the same sort of setup as we have currently with a 'clean' branch with code directly from the official distribution that is merged into the trunk.
2. Use a new installation of the database, with little to none of our existing site's data.
3. Make any modifications to core as needed (and hopefully they won't be).

I had several drupal installations on my server (actually, a friend's server). Everything was working fine until we updated our PHP from Perl 4 to Perl 5. Now, when a user logs in, the session appears to expire almost immediately. For example, when I log in, I try to get to the admin panel, and I get an error that I'm not permitted and I'm no longer logged in.

The only thing that has changed on the server is the upgrade to Perl 5. Now we need Perl 5 for other projects, so downgrading isn't an option.

What can I do to fix the problem?