The site is in fact installed and works fine, but since the install task is reported as failed, you need to run Enable task to be able to use the site.
Full task log: https://gist.github.com/3794271
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | civicrm-another-error.txt | 1.9 KB | omega8cc |
| #3 | drush-en-civicrm-fail.txt | 2.03 KB | omega8cc |
| #2 | CiviCRM-fail1.txt | 20.95 KB | omega8cc |
| #2 | CiviCRM-fail2.txt | 23.08 KB | omega8cc |
Comments
Comment #1
omega8cc commentedAnd the same with 4.2.2
Could you take a look?
Comment #2
omega8cc commentedI have tried to debug this by adding some extra messages:
The result is that the
module_enable(array('civicrm'));is the point where it pseudo-fails.Of course if when replaced with the old
drush_pm_enable('civicrm');it completes the install fine, but doesn't enable CiviCRM module - as known from the issue #1545902: Provisioning the site doesn't enable CiviCRM with any version - tested with Aegir 2.x based on 1.8I'm attaching full install logs for reference.
The question is, how to silence this pseudo-error? Since in fact it does enable the module.
Comment #3
omega8cc commentedFound it! It is because
drush en civicrmthrows this error (see attached result).Comment #4
omega8cc commentedTurns out, there was unrelated extra problem, which is BOA-specific. We symlink platforms for better APC performance, so the
civicrm_modulepathdoesn't include/matchdrupal_basepath, and this causes all kinds of broken paths and related issues then.However, after fixing this with the trick shown below, the install fails with the same HTML-garbage-error.
The trick for BOA:
Attached latest error which still breaks the task, even if the module is enabled.
Comment #5
omega8cc commentedTo get it working reliably with various versions tested, I had to copy some code from Drupal functions into
install.provision.incinstead of call onlymodule_enable(), so it looks like:This code works for 3.4.8 on D6, 4.1.6 on D6 and D7 and 4.2.2 on D7.
Comment #6
bgm commentedWith the ClassLoader fix, are you still getting this error?
Tthe tests running these days are not reporting any issues with 4.2 or 4.3-alpha.
Comment #7
omega8cc commentedI didn't try that again with this extra code removed, just merged in latest head and everything works great, but I will try again with this patch reverted and will confirm if this workaround is still required.
Comment #8
omega8cc commentedI have removed this extra code and it still works for all CiviCRM version I have tested, so it is no longer a problem.
Comment #9
omega8cc commentedOne of our clients just confirmed that all install attempts fail for CiviCRM 4.2.6 (with that pseudo-failed task), even if the site is installed, so my patch is still required to avoid that, at least on previous CiviCRM versions. Not sure why it worked on my own tests on a clean, new install, but indeed, the patch is still required.
Comment #10
bgm commentedClosing this old issue, no activity for 2 years. There have been a lot of changes to cleanup provision_civicrm recently, and it seems to be working well with 4.2 D6/D7 to 4.5. Feel free to re-open if you still run into this issue. Thanks.