CiviCRM Community Forums (archive)

Hi. I just installed 4.0.5 on Joomla 1.7, the way I have installed previous point releases i.e. unstall civicrm, install from /tmp/com_civicrm where I have the internationalised package ready to go.

It just overwrote my entire previous installation - normally it does an upgrade.

I'm restoring from backups now, but it's been a shock! Is the upgrade path supposed to be different?

OK, guilty. I didn't notice that uninstalling is not a prerequisite (I'm sure it used to be?)

Anyway, the "new" install went into my website database, and my civi data is in a separate database. Doing a re-update leads to the software knowing that it is an update but putting the settings files back to pointing at the website database. When an update is being done, where does it look at to work out where to set the settings files? If I just delete the new tables it created in the website database will it default to the civi database (which is what the settings files say) or is it registered somewhere in Joomla where it should look?

Sorry, if I'd RTFM properly the first time....

Thanks, it does for installs where the civi tables and the joomla tables are in the same db. In mine, they're not. That obviously works fine because civicrm.settings.php specifically allows for that.

So on an upgrade/install, what is the script looking for to distinguish between (1) an upgrade for someone whose tables are elsewhere and (2) a new install.

I think that's the problem I've got, and I need to reset whatever flag it is looking at as its making the wrong choice now due to my earlier mistake.