dev/core#1246 fix fatal error on search builder if a core contact type is disabled #15284
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
(Standard links)
|
|
@colemanw can you switch branch to the rc? We should include in 5.17 drop |
|
retest this please |
|
added Merge on pass as added Merge on pass to 5.17 |
|
unrelated fail |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is a more thorough treatment of @eileenmcnaughton's #15279 that makes the code more contact-type agnostic by removing some hard-coded assumptions about what contact types should & shouldn't exist.
https://lab.civicrm.org/dev/core/issues/1246
Before
Fatal error on search builder.
After
Works