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.

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

dev/core#5090 Fix display of multiple autoselect custom fields #29721

Merged
merged 2 commits into from
Mar 18, 2024

Conversation

eileenmcnaughton
Copy link
Contributor

Overview

dev/core#5090 Fix display of multiple autoselect custom fields

This is a regression in the sense that the bug has always existed in the Custom Data loaded by ajax - but the event form newly loads it's custom data that way

Before

See https://lab.civicrm.org/dev/core/-/issues/5090

Note the test data will create the relevant field

After

Saved custom data loads

image

Technical Details

@colemanw - that function is a nightmare!! Is it really still that complicated?

Comments

Copy link

civibot bot commented Mar 14, 2024

🤖 Thank you for contributing to CiviCRM! ❤️ We will need to test and review this PR. 👷

Introduction for new contributors...
  • If this is your first PR, an admin will greenlight automated testing with the command ok to test or add to whitelist.
  • A series of tests will automatically run. You can see the results at the bottom of this page (if there are any problems, it will include a link to see what went wrong).
  • A demo site will be built where anyone can try out a version of CiviCRM that includes your changes.
  • If this process needs to be repeated, an admin will issue the command test this please to rerun tests and build a new demo site.
  • Before this PR can be merged, it needs to be reviewed. Please keep in mind that reviewers are volunteers, and their response time can vary from a few hours to a few weeks depending on their availability and their knowledge of this particular part of CiviCRM.
  • A great way to speed up this process is to "trade reviews" with someone - find an open PR that you feel able to review, and leave a comment like "I'm reviewing this now, could you please review mine?" (include a link to yours). You don't have to wait for a response to get started (and you don't have to stop at one!) the more you review, the faster this process goes for everyone 😄
  • To ensure that you are credited properly in the final release notes, please add yourself to contributor-key.yml
  • For more information about contributing, see CONTRIBUTING.md.
Quick links for reviewers...

➡️ Online demo of this PR 🔗

@civibot civibot bot added the 5.72 label Mar 14, 2024
Copy link

civibot bot commented Mar 14, 2024

The issue associated with the Pull Request can be viewed at https://lab.civicrm.org/dev/core/-/issues/5090

@colemanw
Copy link
Member

@eileenmcnaughton that function is a nightmare!! Is it really still that complicated?

Don't blame me I didn't write it! 😝
But there is some cleanup in order no doubt.

@eileenmcnaughton
Copy link
Contributor Author

test this please

See https://lab.civicrm.org/dev/core/-/issues/5090

Note the [test data](https://github.com/eileenmcnaughton/testdata) will create the relevant field

This is a regression in the sense that the bug has always existed in the Custom Data
loaded by ajax - but the event form newly loads it's custom data that way
Co-authored-by: colemanw <coleman@civicrm.org>
@Detsieber
Copy link
Contributor

Perfect - works as expected now!
Please merge.

@demeritcowboy demeritcowboy merged commit 980f4d3 into civicrm:5.72 Mar 18, 2024
3 checks passed
@eileenmcnaughton eileenmcnaughton deleted the 572_cust branch March 18, 2024 18:59
@eileenmcnaughton
Copy link
Contributor Author

thanks @demeritcowboy @Detsieber

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants