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) »
  • Discussion (deprecated) »
  • Alpha and Beta Release Testing »
  • Joomla upgrade 1.9>2.0b2 db location issue.
Pages: [1]

Author Topic: Joomla upgrade 1.9>2.0b2 db location issue.  (Read 2535 times)

speleo

  • Ask me questions
  • ****
  • Posts: 396
  • Karma: 28
  • CiviCRM version: 4.3.1
  • CMS version: J! 2.5,9
  • MySQL version: 5.1
  • PHP version: 5.3.24
Joomla upgrade 1.9>2.0b2 db location issue.
February 22, 2008, 05:48:10 pm
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

  • 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: Joomla upgrade 1.9>2.0b2 db location issue.
February 23, 2008, 12:51:09 am

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
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) »
  • Discussion (deprecated) »
  • Alpha and Beta Release Testing »
  • Joomla upgrade 1.9>2.0b2 db location issue.

This forum was archived on 2017-11-26.