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

CRM-20676: Tax applied repeatedly on edits of price set events #11455

Merged
merged 1 commit into from
Jan 1, 2018

Conversation

'id' => $params['id'],
'return' => 'tax_amount',
));
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Monish I'm curious to know why this is necessary. The old code was referencing this variable already, just as the new code is. Was it sometimes not present?

Copy link
Member Author

@monishdeb monishdeb Dec 29, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@colemanw for the added unit test it needs default tax_amount information in $this->_values, but unfortunately Contribution.getsingle API doesn't provide value for this attribute, so yes its something not present earlier and there was no UT written, that need tax_amount (until now). Another alternative to deal with it is to set this as one of the default return property as I did here But after discussing with Eileen I decided to fetch its value on demand.

@mattwire
Copy link
Contributor

I had a similar issue on a client site, affecting edits of contributions. To fix, I had to apply this patch and also #11461

@eileenmcnaughton eileenmcnaughton merged commit 38ef254 into civicrm:4.7.30-rc Jan 1, 2018
@eileenmcnaughton
Copy link
Contributor

Merged - this is a tested step forwards - but we need to also check if we need #11461

@monishdeb monishdeb deleted the CRM-20676-rc branch January 1, 2018 10:13
sluc23 pushed a commit to ixiam/civicrm-core that referenced this pull request Jan 10, 2018
CRM-20676: Tax applied repeatedly on edits of price set events
@mlutfy mlutfy added this to the 4.7.31 milestone Feb 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants