Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-10395

Call payment processor's checkConfig method on initial configuration

    Details

    • Type: Bug
    • Status: Won't Do
    • Priority: Trivial
    • Resolution: Won't Do
    • Affects Version/s: 4.2.0
    • Fix Version/s: Unscheduled
    • Component/s: Core CiviCRM
    • Labels:
      None
    • Versioning Impact:
      Patch (backwards-compatible bug fixes)

      Description

      CRM_Admin_Form_PaymentProcessor::buildQuickForm() validates that "user_name" is present, but this is not valid for all payment processors (eg those which configure via URL instead of username). There is a comment on the form rule which says "would be good to make this payment processor specific".

      CiviCRM payment processors are permitted to implement their own validation via the checkConfig() method, so the suggestion in that comment appears to have been implemented.

      In the case of the F2C Donate payment processor, the presence of this form rule requires that a redundant field be retained and populated by the user.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              xurizaemon Chris Burgess
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: