Author Topic: support Drupal's $db_prefix (Read 1796 times)

TwoMice · July 19, 2011, 03:17:06 pm

I have a client who's running two Drupal sites (a "Drupal multisite" installation) that share a single `users` table. This places the users table in a database other than the one defined in CIVICRM_UF_DSN. This is fine, except when running scripts like bin/civimail.cronjob.php.

At present, scripts under bin/ are authenticating with CRM_Utils_System::authenticate(), which in Drupal is hard-wired to search in the `users` table in the CIVICRM_UF_DSN database. Thus, the civimail user can't authenticate.

Is it worth trying to patch CRM_Utils_System::authenticate() to support Drupal's $db_prefix variable? Is there a better way around this problem?

Thanks,
Allen

Eileen · July 19, 2011, 03:53:48 pm

There is a UI setting under admin settings 'CMS integration' where you can set the users table. I do recall a thread talking about a solution where this wouldn't be required - it's somewhere on the forum.....

We use shared user tables a lot & our crons seem to run - presumably because we fill in the CMS integration and / or the table name in settings.php

TwoMice · July 19, 2011, 04:53:16 pm

Thanks, Eileen. That fixed it.

CiviCRM Community Forums (archive)

News:

Author Topic: support Drupal's $db_prefix (Read 1796 times)

TwoMice

support Drupal's $db_prefix

Eileen

Re: support Drupal's $db_prefix

TwoMice

Re: support Drupal's $db_prefix