dev/report#90 - Don't crash search_kit on upgrade from 5.35 #22375
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
https://lab.civicrm.org/dev/report/-/issues/90
Running extension upgrades crashes if you upgrade search kit directly from 5.35 or earlier to 5.40 or later and have an existing search_display. Note that 5.35 was a security release so there are still lots of sites on 5.35 (http://stats.civicrm.org/?tab=sites)
Before
After
Ok
Technical Details
While the right thing might be to do as suggested in https://docs.civicrm.org/dev/en/latest/framework/upgrade/#tips-prefer-simple-sql-semantics-over-apibaodao and rewrite the upgrade steps without using apis, this seems a simpler fix.
Comments