henare / civicrm-eway-recurring-payment-processor Goto Github PK

Trying to run process_recurring_eway_payments.php:
Fatal error: require_once(): Failed opening required 'CRM/Core/BAO/PaymentProcessor.php'

Looks like PaymentProcessor.php has moved:

"Move CRM/Core/BAO/PaymentProcessor.php to Financial directory since it's DAO is there and PaymentProcessorType.php is also there"

http://issues.civicrm.org/jira/browse/CRM-11334?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel

Also the class has changed from CRM_Core_BAO_PaymentProcessor to CRM_Financial_BAO_PaymentProcessor.

To make this script work with CiviCRM 4.3, I had to:

• comment out: require_once 'CRM/Financial/BAO/PaymentProcessor.php'; in the script
• copy PaymentProcessor.php back to Core. ClassLoader is trying to load the file from there, I couldn't find where this call originated (looks like a dynamic look up)
• change reference of CRM_Core_BAO_PaymentProcessor to CRM_Financial_BAO_PaymentProcessor in the script

I have yet to try in prod

got a Invalid managedCustomerID when running in test mode, eway sandbox

Fatal error: Uncaught SoapFault exception: [soap:Client] Invalid managedCustomerID. in /home/sospakis/www/dev/sites/default/files/civicrm/custom_ext/org.civicrm.ewayrecurring/process_recurring_eway_payments.php:271

Apparently there is only one valid ManagedCustomerID which make it harder to test the script. From Eway Token documentation:

The test gateway URL is
https://www.eway.com.au/gateway/ManagedPaymentService/test/ managedCreditCardPayment.asmx
The test username is [email protected] - this is the only username that will work on the test gateway.
The test password is test123 - this is the only password that will work on the test gateway.
The test ManagedCustomerID is 9876543211000 - this is the only managed customer ID that will work on the test gateway.
The test CustomerReference is Test 123 - this is the only customer reference that will work on the test gateway.

Hi, I'd appreciate your help, must be a trivial one.

Normal Payment goes trough fine.
Now for recurring payment, I got this error:

"Payment Processor Error message
9010: Login failed."

My payment page is setup to accept monthly recurring payment.

My eway payment processor urls are the default one for live:

• Site url: https://www.eway.com.au/gateway_cvn/xmlpayment.asp
• Recurring payment url: https://www.eway.com.au/gateway/ManagedPaymentService/managedCreditCardPayment.asmx?WSDL

Any idea ? has Eway changed the url ?

As noted in #1 the plugin is not currently compatible with CiviCRM 4.3.

• Test pending contributions work
• Test scheduled contributions work

If an instalment is paid on Oct 31, then "+1 month" will schedule the next payment on Dec 1, as there is no Nov 31.

I suggest we use the cycle_day column in the Recurring Contribution table to avoid this.

• Pay the first instalment on the day it's scheduled (when the original Contribution is Pending)
• Pay subsequent instalments on the 'cycle_day' of the month
• cycle_day has a value from 1 to 28. If is set to the day-of-the-month for the first instalment, but '29', '30', and '31' round down to '28'
• Thus subsequent payments are a month apart and no months are skipped

Should I go ahead and code this?

Because I am using mail tokens defined by a hook in a Drupal module, I needed to bootstrap the CMS. See kenwest@da0f9a0 for a patch

http://stillmaintained.com/henare/CiviCRM-eWay-recurring-payment-processor

cc/@Vincemd @kenwest @ChrisChinchilla

Currently we only get today's scheduled payments which means if one was missed, say a few days ago, it will never be processed ever again.

It's not out yet but I've already noticed that civicrm/civicrm-core@797b807 will necessitate an update.

There is a bug in PHP which causes to convert the managed_customer_id into an integer which is wrong.
On line 262 of processs_recurring_eway_payments add:

//PHP bug: https://bugs.php.net/bug.php?id=49669. issue with value greater than 2147483647.
settype($managed_customer_id,"float");

otherwise the soap call will change the managed customer id to 2147483647 which is the greatest value of an Integer