GitLab

Created by: eileenmcnaughton

Overview

Move Legacy FirstData processor to an core-extension

This is one of a handful of processors that is in core but we believe is no longer in use.

Before

FirstData is in main CRM_Core_Payment folder, but not enabled on new installs

After

FirstData is moved to a core-extension, enabled only on upgrade for sites with existing payments linked to processors of FirstData type. Extraneous FirstData payment processor records removed on other sites.

Technical Details

Upgrade script not yet written but the plan is 1) Look for any instances of PaymentProcessors linked to the FirstData class. If none exist delete the FirstData row from the civicrm_payment_processor_type table 2) Look for any financial_trxn records linked to any existing FirstData payment processor instance (recurrings are not possible here). If none exist delete from civicrm_payment_processor & civicrm_payment_processor_type 3) If there IS a processor row then install the extension. The install makes no DB changes as this extension is only intended for those who already depend on it existing. As such it is also hidden.

Comments

Planning for complete removal from core is punted for now. However, we should start to see stats on whether it is enabled  for anyone over time. We could use status checks in the extension for messaging, once we have it.