CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Post-installation Setup and Configuration (Moderator: Dave Greenberg) »
  • drupal $db_prefix workaround?
Pages: [1]

Author Topic: drupal $db_prefix workaround?  (Read 721 times)

cgnicholas

  • Guest
drupal $db_prefix workaround?
September 24, 2009, 01:03:57 pm
The Drupal istallation we are bolting CiviCRM onto was installed with the (dreaded) db_prefix item in settings.php, and therefore every table has this prefix.  i.e. "users" is really (in our case) drpl_users, etc.

Therefore, synchronization of pretty much all flavors don't work :-(

Any words of wisdom how to approach this, besides attempt to remove all the prefixes, i.e. reinstall/migrate the Drupal installation?

thanks!
Chris

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: drupal $db_prefix workaround?
September 24, 2009, 02:04:08 pm

goto

Administer CiviCRM >> Global Settings >> Drupal Integration Settings

you can set the user table name there

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Post-installation Setup and Configuration (Moderator: Dave Greenberg) »
  • drupal $db_prefix workaround?

This forum was archived on 2017-11-26.