I just tested this with CiviCRM 3.4.8, CiviCRM 4.0.8 and CiviCRM 4.1.2 and none of them work, so it is probably related to some changes in Aegir/Hostmaster after 1.8 release? Note that there are differences in the install task logs, so it is probably a sign of some other issues.

Comments

omega8cc’s picture

Status: Active » Closed (duplicate)
omega8cc’s picture

Status: Closed (duplicate) » Active

I just tested this again with head, so with patch from #1545652: _provision_civicrm_is_site_context fails to detect CiviCRM and it didn't help. Same results.

omega8cc’s picture

StatusFileSize
new15.37 KB

Please see attached task log. Note that it correctly discovers civi, but doesn't enable it.

omega8cc’s picture

Priority: Normal » Critical

It is exactly the same result as with all three install task logs attached to this issue - civi is discovered in all of them, but not enabled.

bgm’s picture

Weird, the log for 4.1.2 does seem to indicate that CiviCRM was installed:

CiviCRM: found civicrm in packages of sites-all modules
CiviCRM: found civicrm in packages of sites-all modules
CiviCRM: Starting installation...
Settings file generated: /data/disk/o1/platforms/c4b-dist/sites/crm5.o1.linode.us.host8.biz/civicrm.settings.php
CiviCRM installed.
CiviCRM: finished running _provision_civicrm_fixresourceurls()

Could it be only the enabling of the module that failed?

omega8cc’s picture

Maybe.

While 4.1.2 may be still an edge case, as it is pretty new (and we even reverted versions in BOA from 4.1.1 to 4.0.8 and 3.4.8 because it didn't really work back then), the real issue is for sure caused by Aegir.

I just tried it again with previously working 1.0-beta2 and now it no longer works with recent Aegir version.

Basically, while it is discovered, it is either not installed or the final result of the site provisioning is that it is completely disabled - with no errors visible.

omega8cc’s picture

In fact, the install with log attached to #3 above resulted with all civicrm_* tables created, so it is probably installed properly, just not enabled.

bgm’s picture

Title: Provisioning the site doesn't even enable CiviCRM with any version - tested with Aegir 2.x based on 1.8 » Provisioning the site doesn't enable CiviCRM with any version - tested with Aegir 2.x based on 1.8
Priority: Critical » Major

To document progress made on IRC: we fixed a few bugs related to CiviCRM < 4.2. The remaining bug is that drush_pm_enable('civicrm') does not work ("There were no extensions that could be enabled."), and it seems specific to Provision 2.x.

Lowering the priority, since enabling CiviCRM manually is a workaround.

omega8cc’s picture

Note that while enabling CiviCRM manually works for CiviCRM 3.4.8 6.26, CiviCRM 4.1.2 6.26 and CiviCRM 4.0.8 7.14, it doesn't work for CiviCRM 4.1.2 7.14 - it is not possible to enable the module, as it displays error: CiviCRM settings file does not extist. It should be created by CiviCRM install and after clicking on the install link it displays: Oops! CiviCRM is Already Installed

omega8cc’s picture

Status: Active » Needs review
StatusFileSize
new527 bytes

So, you were right!

Replace drush_pm_enable('civicrm'); with module_enable(array('civicrm')); and it enables the module just fine, also for CiviCRM 4.1.2 7.14!

Patch attached.

xurizaemon’s picture

With patch above, I can now deploy an enabled CiviCRM 4.1.2. Thanks!

May be entirely unrelated to this issue, but: After provisioning (using this makefile), the site appears without the Drupal theme for all pages within civicrm/% ... can't see why this is yet. Resource URLs and CIVICRM_UF_BASEURL look OK. Rest of site appears in Garland normally.

To clarify: the first tag in the returned HTML for anything inside civicrm/* is <div id="crm-container" lang="en" xml:lang="en">. It's like it's in snippet=1 land.

omega8cc’s picture

I guess it is cache related, as after the install the top menu looks empty until you will hit one or two links in the admin section, but it is a separate issue, IMO.

bgm’s picture

Status: Needs review » Fixed

Thanks! Commit 3cbd8fd on 6.x-1.x.

@grobot: is this CiviCRM 4.x with Drupal 6.x? Is the UF correctly set to Drupal6 in the civicrm.settings.php? (should be supported by newer provision_civicrm)

Marking issue as fixed, please open a separate one is necessary.

xurizaemon’s picture

Yes, CiviCRM 4.x & Drupal 6 (makefile used) deploys UF correctly as 'Drupal6'.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.