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

Fix payment method fee bug for all calculator types #8204

Conversation

meronogbai
Copy link
Contributor

@meronogbai meronogbai commented Sep 17, 2021

What? Why?

Related to #6942
Related to #8144

This will take care of validating the payment fee input for paypal and cash payment methods and all calculators.

What should we test?

Input a non-number value in the fields of a payment method edit form and try to click on update. You should see a flash error message instead of a 500 error.

Release notes

Validate payment method fee input for all calculator types

Changelog Category: User facing changes

@meronogbai
Copy link
Contributor Author

meronogbai commented Sep 17, 2021

I only tested these changes on cash and paypal payment methods, but this will probably take care of stripe as well. I tried to test it on a stripe payment method, but only paypal express and cash were available as providers in the form.

@meronogbai meronogbai changed the title 6942 fix payment method fee bug all Fix payment method fee bug for all calculator types Sep 17, 2021
Copy link
Member

@mkllnk mkllnk left a comment

Choose a reason for hiding this comment

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

Nice work! 🥇

@filipefurtad0
Copy link
Contributor

filipefurtad0 commented Sep 27, 2021

Hey @meronokbay ,

Thanks for fixing this! I've checked:

  • Paypal
  • Stripe
  • Cash

payment methods in combination with the available calculators:

  • Flat percent
  • Flat Rate (per order)
  • Flexible Rate
  • Flate Rate (per Item)
  • Price Sack

All good! The warning is displayed in all cases. Moving to ready to go!

PS: I thought I'd check what happens regarding shipping methods and enterprise fees, since these use the same calculators, and it seems we have the same issue, which was pre-existing, of course - I've opened this issue and this one, respectivelly.

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

Successfully merging this pull request may close these issues.

4 participants