Upgrading Drupal

Sorry for starting another thread about Fantastico but I think I should share this.

I installed Drupal 5.1 about a year ago using Fantastico De Lux. After reading several threads about Fantastico I decided to uninstall Drupal using Fantastico and then install the latest version (without using Fantastico, since Fantastico doesn't support the latest version). However, Fantastico didn't have an uninstall option, just an update option to 5.3, so I thought why not give it a try?

First there was a warning that I should not upgrade if I have installed modules. I have in fact installed several modules, for instance cck, views, link, adsense and codefilter, but anyway... this is what I did.

1. Make sure all modules are up-to-date (not sure if this is necessary)
2. Backup the database using phpMyAdmin
3. Backup the files in the public_html directory (the root of my Drupal installation)
4. Run the Fantastico update
5. Run update.php (seemed to be part of the Fantastico update)
6. Copy all the modules to the modules directory
7. Run update.php again

So far this seem to have worked like a charm. Plain luck?

Of course the site was in a partly broken state during steps 4-7, but since it's a small site I think nobody noticed.

Hello!

Probably not the best thing to do, but this is what I´ve done when installing Userpoints:

Installed Userpoints version 5.x-3.2
Wanted to use some modules from the Userpoints contributed modules 5.x-3.2.dev.tar.gz but some of them did not work.
Uninstalled and installed Userpoints version 5.x-2.16 with some contributed modules from that version. Run update php. Got warning messages.

Uninstalled and reinstalled version 5.x-3.2. Update.php gave me these messages shown below. Now, I need to go to the database and manually update it, but before I do, I´d like to know what I should look after and how to proceed from this. Thanks in advance.

Drupal database update
user warning: Duplicate column name 'expirydate' query: ALTER TABLE userpoints_txn ADD expirydate INT(11) NOT NULL AFTER reference, ADD expired TINYINT(1) NOT NULL AFTER expirydate, ADD parent_txn_id INT NOT NULL AFTER expired, ADD tid INT NULL AFTER parent_txn_id in /path to/public_html/portal/includes/database.mysql.inc on line 167.
user warning: Incorrect table definition; there can be only one auto column and it must be defined as a key query: ALTER TABLE userpoints DROP PRIMARY KEY in /path to/public_html/portal/includes/database.mysql.inc on line 167.

Hello, can someone help me ? i upgraded my website and i had to log off to do something but when i closed the browser i forgot that it was set to automatically clean the cache and cookies...



Now i can't log in anymore, even using ?q=admin , doesn't work ,



is there any way to login ? or do i have to redo my whole site ? i do have a backup but i have a hunch its not going to solve it. I'm guessing i have to set something in the database to disable the maintenance page right ?

I upgraded from 4.7 to 5.7 over the last couple of days, and I only have one more issue to work out.

I'm using the Andreas09 theme, and I think that the problem is in there.

On my 4.7 version of the site, the gray background (the color behind the white box in the middle of the screen) seems to expand down the screen to fit the right column's blocks. This is how I like it. Upon upgrading to 5.7, the gray background now only wraps to the middle content, but not the right column blocks.

I have several Drupal sites (not multi-site anymore).

For each upgrade of the 5.x series the Update.php script never shows any updates to run. Does that mean I don't really need to disable/re-enable all the modules every time? I mean, is the whole point of disable/re-enable/Update unnecessary if Update.php always says "no updates necessary"? Is "disable/re-enable/Update.php" only needed if I upgrade the contrib modules?

Can anybody point me in the direction of some documentation regarding changes to book.module from Drupal 5.x -> 6.x?

I'm trying to programatically (i.e. at the database level) migrate a large number of books from a 5.x site to the RC3 of Drupal 6, and I've run into some problems regarding the schema changes...

In 5.x, a book page is defined by an entry with type 'book' in the node table, and a corresponding entry in the book table (nid) to define its relationship to a parent page (parent) - if the parent is 0 then it's a top level book. Easy.