This forum is for questions about upgrading an existing Drupal site. Don't forget to read the UPGRADE.txt file that comes with every Drupal download.

Browser closed during upgrading

When I tried running the update.php in a new tab, it told me that I am not logged in as the admin user, so I retardedly went to my open tab with my administration settings and attempted to run it, and now I am screwed and cannot get back into the administer options. Is there anything I can do?

Upgrading 6.0 beta 1 to 2 trouble

I've been testing 6 beta 1 for a little bit (haven't really done any customizations) on a windows server 2003 / IIS / mysql system. I tried the upgrade today a few times; but each time it would just get to the upgrading screen (after the version check page) and sit there without any feedback or advancing to the log page. It did seem to start something as I realized the extra navigation menu I put it wasn't being shown. I believe the upgrade url was ending with an "id=6".

Can one upgrade from 5.1 > 5.3, or must do 5.1 > 5.2 > 5.3?

Sorry newbie upgrade question, but couldn't find answer by searching.

How to manually add the userpoints_txn Mysql DB table?

It looks as if my upgrade from Drupal 4.7 to 5.3 didn't go entirely to plan, and as a result the UserPoints module is missing the userpoints_txn table in the database. People suggested manually adding it using the code in the .install file, but I keep getting SQL formatting errors when I try to add it?

How should I reformat this SQL code to make it work?

Problem in copyin live site to a test site

I plan to upgrade Drupal 4.6.6 to Drupal 5.3 and started by creating a test site from my product site. The main page works fine, but everything else is "Not Found"

According to http://drupal.org/upgrade/copying-your-live-site-via-command-line
I have copied all the files from www.prodsite to www.testsite/drupal53.

Token broken after upgrade?

Hey all, I've been searching to see if anyone else had this issue but not found anything.

Upgraded a drupal 4.7 to 5.3 and discovered that buddylist emails, buddylist invites and ecommerce emails send out untranslated tokens. That is, a user gets an email that reads like this in the case of Buddy adding:
---------
Hi %addee_name,

You are %adder_name's newest buddy on (actual site name appears here)
------------

The invite module sends out emails that read like this:

Pages

Subscribe with RSS Subscribe to RSS - Upgrading Drupal