Joomla upgrade 1.9>2.0b2 db location issue.

[speleo]

When you perform an upgrade (or maybe any install) using civicrm-2.0.beta2-joomla.zip the civicrm.settings.php file sets the db being used as the same as the CMS. I've got mine in a seperate db which is resulting in this error:

Warning: Smarty error: unable to read resource: "CRM/common/fatal.tpl" in /home/bertie/public_html/administrator/components/com_civicrm/civicrm/packages/Smarty/Smarty.class.php on line 1095

Took me a bit of time to work out that I needed to modify this line in both civicrm.settings.php files

Code: [Select]

define( 'CIVICRM_DSN'          , 'mysql://crm_db_username:crm_db_pword@localhost/crm_db?new_link=true' );
maybe a v small table in the CMS db could point to the CiviCRM db to make upgrades less problematic.

[Donald Lobo]

would be nice if we could get some user input in the joomla install process and potentially use a different db. This is not possible with joomla 1.0.x and 1.5, so implementing the below suggestion is a bit harder (since most installs in joomla use the same db)

I suspect your case is more unusual than the norm in joomla. (i also suspect the reverse might be true of drupal!)

lobo