Giving a FFM field a meta key of "give" causes gateway issues
in progress
Alex Coleman
Giving a FFM field a meta key of "give" causes gateway issues. In this case the label was not "give", but any other text - see screenshot. When replicated on a local site a Text field was used, and on the customer's site Dropdown Field was used - so the type of field does not seem to matter when recreating.
Not all gateways have been tested.
Steps to replicate:
Add a field via the Form Field Manager
Use any text as the label, but change the Meta Key to "give"
Default gateway at time of testing: Auth.net
used the following gateways (all gateways not tested):
Plaid + Stripe:
Plaid modal never fires
console: uncaught IntegrationError: The selector you specified...
screenshot attached
Stripe CC
Form spins, throws a 500 error https://localgive.local/?payment-mode=stripe 500
PayPal Payments Pro Credit Card
payment goes through but PAYMENT METHOD in confirmation was listed as the DEFAULT gateway (auth.net in this case)
Authorize.net: seemed to go through ok.
PayPal Donations
screenshot attached
Front end error: The donation could not be charged. Please try again. Reason: The 'AnetApi/xml/v1/schema/AnetApiSchema.xsd:cardNumber' element is invalid - The value XX is invalid according to its datatype 'String' - The actual length is less than the MinLength value.
Log:
post_title:Authorize.net Error
post_content:The donation could not be charged. Please try again. Reason: The 'AnetApi/xml/v1/schema/AnetApiSchema.xsd:cardNumber' element is invalid - The value XX is invalid according to its datatype 'String' - The actual length is less than the MinLength value.
post_parent:0
log_type:gateway_error
file:/Users/my_computer/Local Sites/localgive/app/public/wp-content/plugins/give/includes/gateways/functions.php
line:251
function:add
class:Give_Logging
Ravinder Kumar
in progress