-
-
Notifications
You must be signed in to change notification settings - Fork 824
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
Finish unsharing hacks for contribution preferences form #13047
Finish unsharing hacks for contribution preferences form #13047
Conversation
(Standard links)
|
@eileenmcnaughton Please ping when this one is ready |
…cks into one form
017fbcd
to
2f6c641
Compare
@mattwire @pradpnayak this is rebased now |
* Process the form submission. | ||
* Our standards for settings are to have a setting per value with defined metadata. | ||
* | ||
* Unfortunately the 'contribution_invoice_settings' has been added in non-compliance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, 'contribution_invoice_settings' is being stored in unusual way. Changing this now might cause problems for Sales tax or Deferred revenue since I believe they all rely on this setting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was I too grumpy in my code comments :-)
@eileenmcnaughton I tested this and it works very well now and also the field labels are not printed twice. Also checked 'contribution_invoice_settings' setting variable, it does hold all the Sales Tax settings. Thank you so much for code cleanup. However there is one issue like you mentioned The wysiwig field does show up on my machine. I am not sure about the ACL test file if they have any meaning to this PR. But this is GOOD TO MERGE! Thanks |
Thanks @pradpnayak once this is merged the things I / anyone prepared to help will ideally do are
|
Overview
This is (almost) the last of a series of updates to remove technical debt in the 'preferences' forms.
Before
Hacks to support non-spec settings for invoicing distributed in weird & wonderful places
After
Hacks constrained into the relevant form & commented
Technical Details
Most detail is in https://lab.civicrm.org/dev/core/issues/495
Comments
I have 2 issues still with this
I think it would be easier to merge #13046 first & I'll rebase this. It IS a bit of a hatchett job & is mostly about UI testing on the one form