Author Topic: Problem & Solution when Upgrading from 4.1.0 to 4.2.0 on Drupal 7.15 (Read 500 times)

PrincessAng417 · September 11, 2012, 09:58:57 am

I have one database which Drupal and CiviCRM share.

When upgrading form CiviCRM 4.1.0 to 4.2.0, I encountered the attached error, and I could not get the menus to rebuild. This makes sense because there is no 'dbname.system' table. There is, however, a dbname.drupal_system table.

Therefore, changing line 868 in \sites\all\modules\civicrm\CRM\Utils\System\Drupal.php to:

$q = db_query('SELECT name, status FROM drupal_system WHERE type = \'module\' AND schema_version <> -1');

fixed the problem.

Hope this helps someone else.

totten · September 11, 2012, 10:57:56 am

That's really weird. The code says:

Code: [Select]

    $q = db_query('SELECT name, status FROM {system} WHERE type = \'module\' AND schema_version <> -1');

In Drupal, the normal table name is "system," but Drupal allows site administrators to configure a table prefix or an alternate name (eg "drupal_system" or "test_system"). To facilitate this, Drupal's API allows one to write SQL queries with a special notation -- "{tablename}" -- which means "translate from the normal table name to the real table name." It seems that -- for some unknown reason -- the translation isn't being run properly.

Could you provide:
1. More details about how you configured prefixing/renaming (eg how you did the installation and applied that configuration)
2. More error context -- e.g. if it occurred while running the upgrade (with the progress bar), then which exact step failed? Was there a full a backtrace -- either on the screen or in the log file (sites/*/files/civicrm/ConfigAndLog/CiviCRM*log)?

CiviCRM Community Forums (archive)

News:

Author Topic: Problem & Solution when Upgrading from 4.1.0 to 4.2.0 on Drupal 7.15 (Read 500 times)

PrincessAng417

Problem & Solution when Upgrading from 4.1.0 to 4.2.0 on Drupal 7.15

totten

Re: Problem & Solution when Upgrading from 4.1.0 to 4.2.0 on Drupal 7.15