Timeline for Custom PHP not being picked up
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2018 at 21:07 | comment | added | Pradeep Nayak | I guess Omnipay extension have cron job that deals with recurring contribution. I am not sure but what i would do is change the civicrm_payment_processor.payment_processor_type of existing payment processor to use new SagePay payment processor type as it will resolve any problem with recurring contribution or auto membership renewal. | |
| Oct 7, 2018 at 19:20 | comment | added | Chris Burgess | Link for SagePay PR info: github.com/eileenmcnaughton/nz.co.fuzion.omnipaymultiprocessor/… - if you do use that Omnipay, that's probably where feedback is best directed for now. | |
| Oct 7, 2018 at 19:17 | comment | added | Chris Burgess | Are there any special considerations / warnings for dealing with old contributions (especially recurring ones) which would relate in the DB to the previous SagePay processor? | |
| Oct 6, 2018 at 11:07 | history | answered | Pradeep Nayak | CC BY-SA 4.0 |