Needs review
Project:
Aegir Hosting CiviCRM
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Jun 2016 at 05:00 UTC
Updated:
23 Dec 2016 at 20:20 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
ergonlogicActually, it turns out that it's coming from both
_provision_civicrm_upgradedb()and drush_civicrm_upgrade_db(). We appear to be attempting to do some output buffering, but little of any use is being returned. Either way, I certainly don't think this deserves to be a warning by default.Perhaps for older installations, it was calling a core CiviCRM function? This'd explain the OB stuff. But when calling another drush function, it doesn't make as much sense.
I've cleaned this up in 671b53e, which has resolved this warning for me.
Comment #3
bgm commentedI would prefer keeping this as a "info" message, but OK to not make it a warning.
drush_civicrm_upgrade_db() will output the upgrade notes using this:
That's why hosting_civicrm was capturing the buffered output.
#2734933: CIVICRM_UPGRADE_ACTIVE true fails on AEgir tasks will also avoid running the upgrade uselessly, but agreed that displaying them as a "warning" is not productive, it trains people to ignore all warnings.
Comment #4
ergonlogicI reverted my previous commit, which had just ignored the output.
I've attached a patch that reduces the severity of the log to 'info', and cleans up some code duplication in the process.
Comment #5
ergonlogicNew patch; fixes mis-placed parenthesis.
Comment #6
ergonlogicSee this PR on Github for a rerolled commit: https://github.com/mlutfy/hosting_civicrm/pull/12