Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Filling custom fields not working any more with CiviCRM 5.27+ #68

Closed
bjendres opened this issue Sep 3, 2020 · 2 comments
Closed

Filling custom fields not working any more with CiviCRM 5.27+ #68

bjendres opened this issue Sep 3, 2020 · 2 comments
Labels
bug status:fixed The issue has been resolved (usually by committing/merging code)
Milestone
1.8

Comments

@bjendres
Copy link
Member

bjendres commented Sep 3, 2020 •
edited
Loading

It seem like a change in the handling of custom field types, there has been an internal change in CiviCRM 5.27. Multi-Value fields used to be marked by the html_type "Multi-Select" (and two more "Multi-*").

With 5.27 the html_type was always set to "Select" and the serialize flag was used to mark multi-value fields.

They have added some compatibility code to provide a legacy API (v3), but they didn't cater for html_type search parameters. Therefore XCM doesn't detect these fields as multi-value, and ignores them.

See CORE-1996
@bjendres bjendres added the bug label Sep 3, 2020
@bjendres bjendres added this to the 1.8 milestone Sep 3, 2020
bjendres added a commit that referenced this issue Sep 3, 2020
@bjendres
[#68] workaround for core issue
833adc4
@bjendres bjendres mentioned this issue Sep 4, 2020
Open
bjendres added a commit that referenced this issue Sep 4, 2020
@bjendres
[#68] workaround for CORE-1996
7171155
bjendres added a commit that referenced this issue Jan 12, 2021
@bjendres
[#68] fixed (terrible) typo
b279342
bjendres added a commit that referenced this issue Jan 12, 2021
@bjendres
[#68] fixed (terrible) typo (merged issue/68)
bea6296
bjendres added a commit that referenced this issue Jan 12, 2021
@bjendres
[#68] fixed (terrible) typo (merged issue/68)
89be417
@jensschuppe
Copy link
Collaborator

Will be released with 1.8

@jensschuppe jensschuppe added the status:fixed The issue has been resolved (usually by committing/merging code) label Mar 25, 2021
@bjendres
Copy link
Member Author

released with 1.8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug status:fixed The issue has been resolved (usually by committing/merging code)
Projects
None yet
Milestone
1.8
Development

No branches or pull requests
2 participants
@bjendres @jensschuppe