handle error corner cases

Katalon browser based automation testing

Very incomplete, but hopefully is a useful start.

Ensure newer versions of jquery handle total amount properly

Without this patch, an attempt to submit a webform with a payment option
that totals $0 gets the error: Error: Could not find payment
information.

That's because the check for a total price of $0 fails. It fails for two
reasons:

1. Newer versions of jquery conform to html5 specs that say the data in
the field called "data-amount" should be referred to as simply "amount"
rather than "data-amount"

2. In addition, jquery now tries to convert values to their appropriate
type, so the strict matching of === '0' only matches on the string value
of '0' but jquery is converting the string '0' into the integer 0.

When stripe throws an error, and the original form as an onclick event,
we briefly see the error before the form is submitted according to
the onclick event (i.e. the PreventDefault() and return false
does not have any effect).

This fix removes any onclick attributes at the beginning and only
re-adds them and resubmits the form if we should.

add api and test suite.

refactored IPN to use base IPN class from civicrm

This allows use of webhook in format /civicrm/payment/ipn/N

https://github.com/drastik/com.drastikbydesign.stripe/issues/221

Drupal Webform: Re-enable hook_civicrm_buildForm and comment in different situations we need alterContent and buildForm to load js scripts

mattwire authored 7 years ago and mattwire committed 7 years ago

Always load civicrm_stripe.js if we have a payment processor on the page. This makes sure we always generate a token if the selected processor was stripe

mattwire authored 7 years ago and mattwire committed 7 years ago

Always load stripe.js when on a payment processor page (recommended by stripe for fraud detection).

Our webhook code retrieves every single event sent to us.  But not all of them have a 'customer' property, such as Customer objects, which have an 'id'.

Error on recurring donations Received unknown parameter: name

avoid IDS extension problems

deal with same release date on tags 4.7.2 and 4.7.1

I believe to fix the release date on 4.7.2 best practices say one should create a new 4.7.3 tag with corrected date. It gets a bit messy at this point trying to put a release date of 2017-09-07 in with that tag.

Use setAppInfo function to set CiviCRM information

https://github.com/drastik/com.drastikbydesign.stripe/issues/228