You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It came to our attention in a support ticket that the value of an option in the Ninja Forms payment methods field is case-sensitive. Within Ninja Forms, the PaymentMethods::is_active( $payment_method ) method is used to check if the given payment method is active, before creating the payment.
Would it be beneficial to transform the payment method to lowercase in the is_active() method? Or would that be a potential issue if gateway add-ons can maybe register their own payment methods — with any constant to their liking — in the future?
Would it be beneficial to transform the payment method to lowercase in the is_active() method? Or would that be a potential issue if gateway add-ons can maybe register their own payment methods — with any constant to their liking — in the future?
I'm not in favor of this, let's focus on making the Ninja Forms payment method field less error prone:
It came to our attention in a support ticket that the value of an option in the Ninja Forms payment methods field is case-sensitive. Within Ninja Forms, the
PaymentMethods::is_active( $payment_method )
method is used to check if the given payment method is active, before creating the payment.Would it be beneficial to transform the payment method to lowercase in the
is_active()
method? Or would that be a potential issue if gateway add-ons can maybe register their own payment methods — with any constant to their liking — in the future?Internal Help Scout ticket: https://secure.helpscout.net/conversation/2067045031/24787/
The text was updated successfully, but these errors were encountered: