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

Do not add custom fields of custom groups with style other than "Inline" to forms where in the UI those fields are loaded via Ajax #31495

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jensschuppe
Copy link
Contributor

Fixes dev/core#5613

Prevent data loss for forms of non-Contact entities with custom groups of style other than Inline.

This fixes a regression for code that uses the style attribute in a way that can't be built through the UI (as it can't be set for other entities than Contact).

…ne" to forms where in the UI those fields are loaded via Ajax
Copy link

civibot bot commented Nov 18, 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 master label Nov 18, 2024
@colemanw
Copy link
Member

@jensschuppe if this is a regression then the PR should be against the 5.80 branch.

@jensschuppe
Copy link
Contributor Author

Well, it depends … the scenario where this leads to data loss can't be built through the UI, so I can't judge.

@aydun
Copy link
Contributor

aydun commented Nov 18, 2024

That makes sense - the AJAX in CRM/common/customDataBlock.tpl only pulls in Inline so the related addCustomDataFieldsToForm() should do the same. style has to be set by API (other than Contacts) but you need some other mechanism to display those fields.

Looks good to me.

@jensschuppe jensschuppe marked this pull request as ready for review November 19, 2024 10:09
@jensschuppe
Copy link
Contributor Author

Maybe @eileenmcnaughton should have a look, as the underlying problem got exposed with #30569 …?

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.

3 participants