artfulrobot
commented
7 years ago Hi. I'm on holiday for a couple of weeks but a quick reply as I know what it feels like to have a broken site!
From memory (!) there's not much different with this payment processor than others. It creates
- a payment processor type
- a pair (live/test) of payment processors
- a payment instrument
Then when you use it at all you'll get contribution and recurring contribution records. Importantly, these records will reference the payment processor ones. I think that's what causes the grief on uninstall (I'm sure I've encountered that). Also if you set up contribution pages these will also create references. You would need to ensure all these records are completely deleted, then delete the payment processor, before uninstalling.
Hope that helps Rich
jonacaz
Have tried installing on a test machine and a production/live site, on which both the vedaconsulting module and other payment processors had been installed. I haven't got this payment processor to work properly yet. But slightly worrying is that if I attempt to uninstall this artfulrobot extension on the live site, the live site goes down with a HTTP 500 error; one of the PHP files in this extension is expected and missing. Fortunately I was able to us drupal drush to re-enable the extension. I think this is a self inflicted problem. But what I would really like to be able to do is clean up these two civicrm installations and remove all traces of previously installed (payment processor) extensions, and start again. Reading elsewhere that it appears to be very difficult. I have compared my test civicrm database pre and post extension installation. Installing an extension inserts records in various tables and it's not clear to me, without going through the code and may be even stepping through the code, how the database is changed. I should have taken a database snapshot before i started! Any thoughts about cleaning up gratefully received.