Closed (works as designed)
Project:
Sunlight Congressional Districts (with optional CiviCRM integration)
Version:
6.x-3.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Jan 2011 at 18:16 UTC
Updated:
2 Jan 2014 at 19:06 UTC
Jump to comment: Most recent
Comments
Comment #1
dalinAre you trying to upgrade from 6.x-1.x? If so note that the way that we now use table prefixes rather than separate db connections. Please review README.txt and admin/reports/status for all the details.
Comment #2
christok commentedThanks for the response. We recently upgraded from 6.2.x, although I never actually got it working (not sure if this is related; quite possibly is).
At any rate, I completely uninstalled the module by deleting the files, tables, variables, and flushing the cache. When I reinstalled - following directions in both readmes - I got the same behavior.
I managed to work around the problem by adding the following function to cd_sunlight.module (civi_query), then replacing instances of db_query with civi_query:
function civi_query($querystring) {
db_set_active('civicrm');
$result=db_query($querystring);
db_set_active('default');
return $result;
}
One interesting aside to this regarding table prefixes... when I set the table prefixes in settings.php to "civicrm_", the module kept trying to query tables with the prefix "civicrm_civicrm_". I had to go back and change the settings prefixes to "". Strange, eh?
Comment #3
dalinWhen you setup the table prefixes did you follow the installation instructions and use what CiviCRM outputs at
civicrm/admin/setting/uf
?
Are you sharing a database between CiviCRM and Drupal? If so then your prefix would be ''. If your CiviCRM DB is called 'civicrm' then the prefix is 'civicrm.'.
Comment #4
dalin