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.

Error on updating D6 --> D7

I upgraded several sites thus far without issues, but somehow on the latest update I get this error:


The following updates returned messages

system module

Update #7053
Failed: PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'user-menu' for key 1: INSERT INTO {menu_custom} (menu_name, title, description) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2); Array ( [:db_insert_placeholder_0] => user-menu [:db_insert_placeholder_1] => User Menu [:db_insert_placeholder_2] => The User menu contains links related to the user's account, as well as the 'Log out' link. ) in system_update_7053() (line 2408 of /modules/system/system.install).

I checked the forums but couldn't really locate any solution, perhaps I missed something. Basically there are 19 updates left, the rest went fine.

Below the list of updates that needs to be done:

system module

7053 - Upgrade standard blocks and menus.
7054 - Remove {cache_}.headers columns.
7055 - Converts fields that store serialized variables from text to blob.
7057 - Increase the size of session-ids.
7058 - Remove cron semaphore variable.
7059 - Create the {file_usage} table.
7060 - Create fields in preparation for migrating upload.module to file.module.
7061 - Migrate upload.module data to the newly created file field.

6.20 to 7.0: Table block_node_type doesn't exist

I'm getting this unrecoverable error when upgrading from 6.20 to 7.0:

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: http://[site]/update.php?id=533&op=do StatusText: Service unavailable (with message) ResponseText: PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table '[db].block_node_type' doesn't exist: SELECT module, delta, type FROM {block_node_type}; Array ( ) in node_block_list_alter() (line 2374 of /home/rokur/[site]/modules/node/node.module).

My site is quite standard Drupal 6.20, except for these modules: AddToAny 6.x-3.3, BUEditor 6.x-2.2, Facebook Like Button, Mollom 6.x-1.15, Pathauto 6.x-1.5, Token 6.x-1.15, Archive 6.x-1.4, Google Analytics 6.x-3.2, and an additional theme Pixture Reloaded 6.x-3.2.

I also try to keep optional core modules to a minimum: Color, Comment, Contact, Database Logging, Forum, Help, Locale, Menu, OpenID, Path, PHP Filter, Ping, Profile, Search, Statistics, Syslog, Taxonomy, Throttle, Tracker, Trigger, Update Status and Upload.

The site status report says that everything is OK.

I disabled the additional modules and the additional theme, before upgrading. I also changed the default language from additional Faroese to English, just to be as close to standard as possible.

Drupal 6.20 to Drupal 7

I am attempting to upgrade from Drupal 6.20 to 7.0. However, when I run update.php, i get this error message:

DatabaseSchemaObjectExistsException: Table role_permission already exists. in DatabaseSchema->createTable() (line 630 of /var/www/drupal/includes/database/schema.inc).

Anyone know how to fix this?

How to modify default theme in variable table with Drupal 7?

Hey everyone, thanks in advance for the help. Here is my problem

Today I upgraded a drupal 6 installation to drupal 7, should have been a simple upgrade but things did not go as planned.

The site was a drupal 6 acquia drupal install, which uses a customized version of the garland theme.
Long story short, after the update was completed, it tried to continue using the d6 version of garland, and obviously no content is rendering.

So this seemed simple enough, make a quick change in the variable table to make bartik the default theme right?

javascript/autocomplete errors after 6.20 upgrade

Having a heck of a time hunting down a bug that is active site-wide, doesn't seem to be related to a theme or any specific module, but it has something to do with javascript, ajax and/or the autocomplete feature. I recently upgraded to 6.20 and did the same for a number of modules.

When the error occurs, a pop-up window is generated (in both Chrome and IE) stating something along the lines of:

An error occurred.
/facebook_status/js
(no information available).

The 2nd line varies depending on which module is affected at that time; other messages state /fbsmp/js or http://mysite.ca/relationship_types/autocomplete.

Been trying several possibly related solutions found here, including modifying autocomplete.js (http://drupal.org/node/487826), turning off aggregator module (http://drupal.org/node/962542), as well as other suggestions to try disabling the devel module and anything else that may add javascript to the bottom of a page.

So far, no luck, and I'm out of ideas. Nothing is showing up in the error logs. Any suggestions?

Thanks,
Brad

===

Some site info:

Drupal 6.20
CTools CSS Cache Exists
File system Writable (public download method)
MySQL database 5.1.41
PHP 5.3.2-1ubuntu4.7
PHP memory limit 128M
PHP register globals Disabled
Unicode library PHP Mbstring Extension
Update notifications Enabled

can I keep settings.php from Drupal 6 in new Drupal 7?

I changed core files and could not access update.php.

So I am wondering now if I should keep settings.php from Drupal 6 in new Drupal 7? or maybe I should delete old settings.php of D6, copy default.settings.php of D7 and rename it to obtain new settings.php.

Pages

Subscribe with RSS Subscribe to RSS - Upgrading Drupal