**This patch will break your site if you try to upgrade.**

CiviCRM 4.7 removed getConfigSettings() and getBestGuessSettings(), changing a pretty major dependency of the dositemove fork we use to migrate sites: https://github.com/civicrm/civicrm-core/commit/4f240ac1294f2cd72ba4cff2b...

I patched _provision_civicrm_do_site_move() in provision_civicrm.inc with the same changes and it seems to work for new sites. Maintaining compatibility with < 4.6 versions sounds possible but not worth it.

As far as my tests go, this works for new sites, but doesn't allow a smooth upgrade, so I'm marking it as "needs work". It still appears useful if you want to be able to create and clone sites from 4.7.1 on up (did not have time to test with 4.7.0). I'm posting it now because that's as much time as I can invest in this for today, but I'm hoping we can work together on this, as (I think?) 4.7 contains security updates.

Again: **This patch will break your site if you try to upgrade.**

I'm including my upgrade log in case someone is googling this, or if anyone has any idea of the root of the problem.

CommentFileSizeAuthor
#5 hosting_civicrm-support_4.7-2663112-5.patch4.9 KBacrollet
civicrm-upgrade-aegir-log.txt85.04 KBgboudrias
hosting-civicrm-civicrm-4.7.x.patch8.92 KBgboudrias
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

gboudrias created an issue. See original summary.

gboudrias’s picture

gboudrias CreditAttribution: gboudrias commented
Issue summary: View changes
bgm’s picture

bgm CreditAttribution: bgm commented

> "Maintaining compatibility with < 4.6 versions sounds possible but not worth it."

While support for CiviCRM 4.4 was dropped on 1st February 2016, I think it's a bit quick to remove hosting support.

However, I totally support cleaning up that old ugly code.

Can we call drush_civicrm_update_cfg() from the drush module? (this way it's version-agnostic).

sluc23’s picture

sluc23 CreditAttribution: sluc23 commented

Agree with @bgm that removing hosting support for CiviCRM 4.4 it is quite early. We still have most of our CiviCRM in 4.4 planning to migrate them to 4.6 (or 4.7 if it's solid enough) at some point of this year.

Now a days, there are many CiviCRM installations with different versions out there and I think it's very important to have a clearer roadmap and publish it, if at any point hosting_civicrm breaks compatibility with older CiviCRM version.

We are able to support & testing if needed.

acrollet’s picture

acrollet CreditAttribution: acrollet at roomify - online and open source reservation solutions commented
FileSize
hosting_civicrm-support_4.7-2663112-5.patch4.9 KB

Patch above doesn't apply, simply attaching a patch that does. (I have no input on the larger discussion)

bgm’s picture

bgm CreditAttribution: bgm at Coop SymbioTIC commented

Can you try this patch instead?
https://github.com/mlutfy/hosting_civicrm/pull/1/files

In short:

   // Update database settings for the directory paths
-  _provision_civicrm_do_site_move();
+  drush_civicrm_update_cfg();
bgm’s picture

bgm CreditAttribution: bgm at Coop SymbioTIC commented
Status: Needs work » Needs review

  • bgm committed cfb8501 on 7.x-3.x 
    Issue #2663112: Support CiviCRM 4.7 and use drush_civicrm_update_cfg()...
bgm’s picture

bgm CreditAttribution: bgm at Coop SymbioTIC commented
Status: Needs review » Fixed

Committed to 7.x-3.x

Status: Fixed » Closed (fixed)

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