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.

Single code base upgrade mechanisme

I have installed Drupal with a single code base for all vhosts of my server.
Now I need to keep the code up to date for drupal core, modules and themes...
Hopefully this can be automated...

Any idea's?

When a theme/module/core element developer discovers a bug and fixes it... How do I get this in my single code base?
Trough CVS? but isn't that used as development for the next generation? Or is it "Save" to use the CVS HEAD in production?

Upgrading weblinks problem

I recently upgraded to 4.7 which went incredibly well, much to my surprise. Anyway I had 150 links using weblinks. However when I upgraded to the new weblinks my counters went to zero. Is there a way to alter the counter to return it to the previous number of visits as i took a record of this.

Regards

Douglas

Migartion problem

Hi,

I had my drupal running in my Debian Etch and had no problems, but I wanted to move to gentoo, so I did a dump of mysql and copied all /var/www/drupal directory in order to install drupal in new site...

Well, I don't know what has happenened, but in new host (with same apache2 but I'm not sure if Etch uses php5, gentoo does) I get this errors in the browser when I try to load drupal site:


warning: array_keys() [function.array-keys]: The first argument should be an array in /var/www/localhost/htdocs/drupal/includes/menu.inc on line 916.

warning: Wrong parameter count for min() in /var/www/localhost/htdocs/drupal/includes/menu.inc on line 916.

warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/localhost/htdocs/drupal/includes/menu.inc on line 331.

warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/localhost/htdocs/drupal/includes/menu.inc on line 334.

warning: Cannot modify header information - headers already sent by (output started at /var/www/localhost/htdocs/drupal/includes/common.inc:384) in /var/www/localhost/htdocs/drupal/includes/common.inc on line 99.

warning: array_keys() [function.array-keys]: The first argument should be an array in /var/www/localhost/htdocs/drupal/includes/menu.inc on line 916.

Lot of errors during upgrade from 4.6.x to 4.7.0

Hello there,

I'm preparing the upgrade of my website, working on a backup imported on a test site. When upgrading, I have a lot of errors, and the main wrong behaviour of the freshly upgraded website (from what I've been able to see until now) is that the content of the "Primary Links" has been replaced by the "Navigation menu" content, and it seems there's no way to recreate properly my "Primary Links".

The errors are typically (see the complete log at the end of this post):

  • Unknown fields
  • Already existing table
  • Multiple Primary Keys defined
  • Already used field name
  • Unable to drop field name
  • A duplicated Key field

My question are:

  • What action must I take to repair my database ? It's really unclear to me, looking at the logs.
  • Are these errors linked to the third-party modules I have used, and should I remove them before I upgrade ? Do I simply need to remove some files in $ROOT/modules/, or is this less trivial ?

Thanks for any help.

Following are the logs,

should I manually correct database after fail upgrade step? and how?

hey all-

I had a failed database upgrade moving from 4.6.6 to 4.6.8 on my way to 7.X.

Can someone tell me the steps I supposed to take. What is meant by manually update the dbase? Do I clear the whole table and reinsert it?

Can I revert the update?

here is my failure:

2005-03-03

2005-03-18

ALTER TABLE {poll} CHANGE voters polled longtext 
FAILED

2005-03-21

ALTER TABLE {term_node} ADD PRIMARY KEY (tid,nid) 
FAILED

when a database upgrade fails, help

Hey all-

Can someone tell me what my options are if a database update fails. I am moving from 4.6.6 to 4.6.8. i had the following failures:

Pages

Subscribe with RSS Subscribe to RSS - Upgrading Drupal