dev/financial#84 - Fix upgrade failure. Thin-out activation logic for sequentialcreditnotes
.
#16971
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This fixes an issue with running the upgrade on certain builds. It addresses the problem by reducing the number of services/layers involved with activating the
sequentialcreditnotes
extension.Related: https://civicrm.stackexchange.com/a/35260/93
Steps to reproduce
wp-demo
with Civi 5.21Before
(1) The upgrader activates
sequentialcreditnotes
using theExtension.install
API(2) The upgrader freezes on "Upgrade DB to 5.24.alpha1". The
CiviCRM.log
includes:After
(1) The upgrader activates
sequentialcreditnotes
using a SQL insert.(2) The upgrade completes. After installation, the
sequentialcreditnotes
extension is active.