When Completing CiviCRM Install No Notification Is Given

The only reason it is possible to configure CiviCRM at all is because the install isn't using the Drupal bootstrap... or any WordPress or Joomla code. This install is not the civicrm Drupal module install, but the CiviCRM core install... the same code used for WordPress and Joomla. You can't run the config or .install of any normal Drupal module before Drupal is installed. You must install CiviCRM before Drupal because the civicrm module is a dependency and is checking to see if the civicrm.settings.php exists among other things. Normally that message is triggered after you enable the civicrm module and shows up in you Status report until you run the core install. In an install profile, if the requirements of a module included in the profile's .info are not met it shows the status message during the Drupal install. In the civicrm modules's case it links directly to the CiviCRM's install.php. Because of this order of operation, you won't be able to finish the Drupal install until the civicrm.settings.php is successfully created. If you can't get CiviCRM installed, you can't install Drupal. But when you successfully install CiviCRM, Drupal still isn't configured so there are very little functionality.

It is CiviCRM that kicks the user back the Drupal root when completed the install is completed. Since Drupal isn't configured, you end up back in the install process. Any "install completed" message would need be displayed in the CiviCRM code before kicking you back to the Drupal install process. That change would also change the install process for WordPress and Joomla. While it's possible to get a patch like that into a future CiviCRM release, you'd need to convince the CiviCRM team to make the advantage to Drupal is worth changing the process and documentation for all platforms. Seems unlikely.

Another option would be to duplicate the civicrm module's requirement check to the .profile and show a warning if the civicrm.settings.php file isn't there and a success message if it is. I'm not going to put any more time into this profile until the next CiviCRM release and even then I'll mainly be removing patches from the profile's .make as they are added to CiviCRM.

If someone else submits a patch for this, I'd be glad to test it. Setting as 'works as designed' until then.

This turned out to be easier than I was making it. The problem with the install.php file was that when it tried to call Drupal hooks from the bootstrapped state, Drupal immediately recognized that Drupal wasn't installed yet and kicked the user back to the first step of the install. To fix this, we changed 2 files. The drupal/civicrm.install file is where the link to start the CiviCRM install is trigger since it is a requirement. Adding the profile and locale variables to the query string allows us to reuse those in the install.php when the CiviCRM part of the install is complete.

Updating install error message to address part of the issue in #1977220: Pantheon: CiviCRM Settings do not exist

This patch needs to be updated for CiviCRM 4.4.3

closing old issues

Updated patch for Civi 4.6