Joomla upgrade process doesn't respect having different CiviCRM and Joomla databases
If CiviCRM is using a different database than Joomla (CIVICRM_UF_DSN and CIVICRM_DSN are not the same), the Joomla upgrade process writes the new civicrm.settings.php files with both set to
This causes some chaos when the upgrade is "done" as both settings files need to be updated quickly, and Civi unnecessarily creates all its tables again in the Joomla database.
A possible fix would be to have civicrm_config get passed CIVCIRM_UF_DSN from civicrm_source and parse it, using those values for dbUser
, dbPass
, dbHost
, dbName
instead of the $jConfig
values. The function already gets passed site, credential & sign keys.
I haven't worked on a PR but will probably have time in the next week or two if there's interest.