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.

Upgrading from 4.7 to 6 - delete certain tables to make install 'clean' as possible?

Hi,

We're upgrading a large site, opendemocracy.net, from Drupal 4.7 to Drupal 6. Our existing install has a lot of superfluous tables in the database from once-used modules we won't be using: ideally, we wouldn't keep these, or our old blocks, etc. This is because: (a) it'd be nice to keep the database as small as possible, (b) it'd be nice for new blocks to start at ID 1, etc., (c) as clean an install as possible should minimise any problems (for example, our crufty old install has some strange problems, e.g. not letting us create any new blocks).

All we really want to keep is our nodes (plus comments), taxonomies, files, statistics, users, path aliases, and one custom table. I've tried copying the tables that I think govern these into a fresh 4.7 install and then upgrading from this, and it appears to work. My questions are: would this work? Is it a good idea? Is there a better way to achieve some of the same goals?

PS: There's also a separate issue with our upgrade involving merging just nodes and taxonomies from a separate Drupal 5 install, but I've put that here: http://drupal.org/node/605156

Here are the tables I think are all we need to keep:

audio
audio_attach
audio_image
audio_metadata
comments
files
node
node_ACCESS ??
node_comment_statistics
node_counter
node_revisions
node_type
od_story
term_data
term_hierarchy
term_node

Why does upgrade.php change to install.php and version numbers go down?

I'm REALLY confused.

Why does upgrade.php change to install.php? Is it supposed to do that?

I watched the video at http://learnbythedrop.com/drop/70 about upgrading to 6.3, yet I'm trying to upgrade to 6.14 -- this all makes NO sense to me.

upgraded from drupal 5.1 to 5.20

After upgrading from drupal 5.1 to 5.20 I am receiving the following error. This error cause nothing to display on my website. I am able to get to the admin panel..

warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/style.css) is not within the allowed path(s): (/var/www/vhosts/cyberbellum.com/httpdocs:/tmp) in /var/www/vhosts/cyberbellum.com/httpdocs/includes/theme.inc on line 68.

This page displays on my website..

Welcome to Cyberbellum

* View
* Edit
* Revisions

My date and CCK modules don't register as updated

It seems that my Drupal installation has given up trying to update the module versions.

I have 'date' wanting a critical update and a few others recommend updating.

All of these have now been updated in the code, though the admin/build/modules page is not updating and continues to claim that these updates are needed.

update.php seems to execute with no issues.

admin/reports/updates has a mysterious green message 'Attempted to fetch information about all available new releases and updates.' - it is green so I assume it is not an error per se...?

upgrade problem

I upgraded from 6.13 to 6.14 but I get this error message when I go to the site:

Fatal error: Cannot redeclare e11u() (previously declared in /home/bloom/public_html/index.php(1) : eval()'d code:1) in /home/bloom/public_html/sites/default/settings.php(1) : eval()'d code on line 1

I have reinstalled the backup of the previous version and the DB backup, apparently successfully, but the error message is the same.

Advice much appreciated.

Problem with content module with v. 6,13 and higher

Hi,

I was with Drupal version 6,12 and upgraded it to 6,14.

Then I got this error when I activate comments in node :

Pages

Subscribe with RSS Subscribe to RSS - Upgrading Drupal