Custom Field edit hook crashes if custom fields enabled for option values #1016
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
Just updating this one call from api3 to api4 seems to fix it.
It seems that in the Custom Field edit hook this call with api3 attempts to access the custom field before it's fully created, causing a fatal. You are left with a half created custom field, which causes general havoc on your system.
With api4, no such problem.
Steps to reproduce (D10, at least as far back as Civi 5.75, also on Civi master)
Before
After
Comments
Admittedly custom fields on OptionValues is a bit of a strange situation, but it seems to generally work fine apart from this.