Answers.Body: <p>The SagePay extension from Circle is outdated and is not supported for 5.x version. Mattwire has integrated sagepay payment processor in Eileen's <a href="https://civicrm.org/extensions/omnipay-multiprocessor-extension" rel="noreferrer">CiviCRM OmniPay Multiprocessor</a> extension. The simplest, easy and recommended solution would be to install the omnipay extension from Matt's git <a href="https://github.com/mattwire/nz.co.fuzion.omnipaymultiprocessor/archive/sagepay.zip" rel="noreferrer">repository</a>(sagepay branch). Move old payment processor from all Contribution and event pages to new sagepay payment processor either by running sql or updating manually. </p>
  
  <p>HTH</p>
  
  <p>Pradeep</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-07T19:17:50.193Z
Answers.Text: 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?
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-07T19:20:28.413Z
Answers.Text: Link for SagePay PR info: https://github.com/eileenmcnaughton/nz.co.fuzion.omnipaymultiprocessor/pull/42 - if you do use that Omnipay, that's probably where feedback is best directed for now.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-07T21:07:26.810Z
Answers.Text: 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.
Answers.UserDisplayName: Pradeep Nayak
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-06T11:07:31.477Z
Answers.LastActivityDate: 2018-10-06T11:07:31.477Z
Answers.UserDisplayName: Pradeep Nayak
Body: <p>I've been pulling my hair out trying to get this working. There is a file in core that throws up errors using the SagePay extension from Circle. I can edit the core .php file and fix the problem. Obviously each time I update it is overwritten. So I have created the same directory structure under civicrm_custom_php and added the edited file. Directory paths are correct, but the file in custom isn't being picked up. Any hints or tips really appreciated on getting this working. I am running CiviCRM 5.6.0 on Drupal 7.</p>
  
  <p>Thanks</p>
  
Tags: <php>
Title: Custom PHP not being picked up
ThreadText: # Custom PHP not being picked up
  
  (Asked by: username_0 on 2018-10-06)
  
  I've been pulling my hair out trying to get this working. There is a file in core that throws up errors using the SagePay extension from Circle. I can edit the core .php file and fix the problem. Obviously each time I update it is overwritten. So I have created the same directory structure under civicrm\_custom\_php and added the edited file. Directory paths are correct, but the file in custom isn't being picked up. Any hints or tips really appreciated on getting this working. I am running CiviCRM 5.6.0 on Drupal 7.
  
  Thanks
  
  **Tags:** php
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-10-06. Score: 4
  
  The SagePay extension from Circle is outdated and is not supported for 5.x version. Mattwire has integrated sagepay payment processor in Eileen's [CiviCRM OmniPay Multiprocessor](https://civicrm.org/extensions/omnipay-multiprocessor-extension) extension. The simplest, easy and recommended solution would be to install the omnipay extension from Matt's git [repository](https://github.com/mattwire/nz.co.fuzion.omnipaymultiprocessor/archive/sagepay.zip)(sagepay branch). Move old payment processor from all Contribution and event pages to new sagepay payment processor either by running sql or updating manually.
  
  HTH
  
  Pradeep
  
  > **Comments:**
  > **username_2**: 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?  
  > **username_2**: Link for SagePay PR info: https://github.com/eileenmcnaughton/nz.co.fuzion.omnipaymultiprocessor/pull/42 - if you do use that Omnipay, that's probably where feedback is best directed for now.  
  > **username_1**: 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.  
  
  ---
  
  