eileenmcnaughton / nz.co.fuzion.omnipaymultiprocessor

Omnipay Multi Processor Payment Processor For CiviCRM
Other
13 stars 44 forks source link

Payment processor list not updated #20

Open roland-jungwirth opened 7 years ago

roland-jungwirth commented 7 years ago

Running on Wordpress/CiviCRM.

  1. Install the extension.
  2. Add Omnifast-Payfast gateway in composer.json
  3. Add payfast gateway and delete all others (see attachment).
  4. Go to Administer > System Settings > Payment Processors.
  5. Add payment processor.
  6. The list is still default, payfast doesn't exist (see attachment) dropdown

    processors.mgd.php.txt

eileenmcnaughton commented 7 years ago

You need to add payfast to the list of processors by updating the .mgd file - the readme text in the file should help

roland-jungwirth commented 7 years ago

Thank you for your answer. Yes, I have done that. I've removed all others and only have the Payfast processor:

`return array( 1 => array( 'name' => 'OmniPay - PayFast', 'entity' => 'payment_processor_type', 'params' => array( 'version' => 3, 'title' => 'OmniPay - PayFast', 'name' => 'omnipay_PayFast', 'description' => 'PayFast Payment Processor', 'user_name_label' => 'Username', 'password_label' => 'Password', 'class_name' => 'Payment_OmnipayMultiProcessor', 'url_site_default' => 'http://unused.com', 'url_api_default' => 'http://unused.com', 'url_recur_default' => 'http://unused.com', 'url_site_test_default' => 'http://unused.com', 'url_recur_test_default' => 'http://unused.com', 'url_api_test_default' => 'http://unused.com', 'billing_mode' => 4, 'payment_type' => 1, ), ),

);`

eileenmcnaughton commented 7 years ago

Removing the others will probably cause problems - but if you flush the system it will try to create the new one - you can do it through the api - civicrm_api(''System', 'flush', array()); or by disabling & re-enabling the extension

shifthappens commented 7 years ago

Disabling and enabling the extension usually helps to load in new payment processors. @eileenmcnaughton maybe a good idea to add this to the readme. I had the same problem until I re-enabled the Omnipay extension within WordPress.