In some CiviCRM's whith some extensions installed, most of the AEgir tasks fail due to CIVICRM_UPGRADE_ACTIVE mode set to true.

The CIVICRM_UPGRADE_ACTIVE is causing problems and we should probably only set it when we are doing a migration task.

Aegir seems to flush the CiviCRM cache while extensions are disabled, and this makes permissions and other settings lose their configuration.

Comments

sluc23 created an issue. See original summary.

bgm’s picture

bgm commented

Tentative patch here:
https://github.com/mlutfy/hosting_civicrm/pull/7

There was a bit of monkey-patching in the code handling upgrades. This will require more manual testing.

I also suspect that we can push this further in: #2713737: CiviCRM 4.6 to 4.7 upgrade SQL error by only setting the CIVICRM_UPGRADE_MODE if we are doing a migrate. When this constant is defined, CiviCRM will not load extensions, which can cause other errors (such as trying to disable a payment-processor, which will fail if there are contributions that used that processor).

  • bgm authored 1edf9b4 on 7.x-3.x 
    Merge pull request #7 from mlutfy/7.x-3.x-issue2734933

Issue #2734933:...
  • bgm committed 578b219 on 7.x-3.x
    Issue #2734933: only set CIVICRM_UPGRADE_ACTIVE when necessary.
bgm’s picture

bgm commented
Status: Active » Fixed

Merged in 7.x-3.x.

This passed the new tests and has been working well for me in prod.

Status: Fixed » Closed (fixed)

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