How to remove a payment module?

[Kent Multer]

I have a client who needs to uninstall an old payment module. To keep a long story short, I'll just say that there's a reason why we need to actually remove it, not just deactivate it. Of course, the store won't allow that if there are any orders in the DB that were processed by that module. So I'll have to fiddle with the DB.

It's easy enough to set the reference count to zero in the StoreModules table, in which case the store will allow me to uninstall the module. But there will be a lot of old orders in the store that still have that module's ID in the pay_id field of the OrderPayments record. If an admin user tries to view one of these orders, that might produce runtime errors. So I'm thinking that I should also zero out the pay_id field for those orders ... but will the store function in that case, without throwing errors? Any other advice on how to do this?

Thanks --

[Bruce - PhosphorMedia]

What about creating a dummy version of that module? You could probably find a developer to build one cheap :)

[Kent Multer]

Actually, I wrote the module. And Yes, I considered writing a "new version" that doesn't do anything; but Thanks for the idea! I'd prefer to just remove the module, if I can do that without breaking something.

[Bruce - PhosphorMedia]

If the orders are being kept for a reason, then to me it actually makes sense to make a dummy copy that just reports, "yup, this is the module that was used". That being said, my bad memory says it will fail silently if the module id is not found. You could test this theory by creating a new test order, changing the module id to one that doesn't exist and access that order to see what happens.

[ids]

Kent,

You could archive orders to be able to remove the payment or other connecting modules to the order. Doesn't sound like that's an option right now.

One thought I have, order data is dumb. The only thing I am aware that connects the order from whatever is payment data. So, batch and refund processing for whatever is available in the order, pointing to the CC charge for instance. There might be a good chance that data isn't needed any longer any way for those orders. So, removing the module id and pay id, etc, is likely the way to go. Not sure about shipping, or tax modules, etc.

However, not having original payment info/shipping info in an old order shouldn't affect the way Order history works. A returning customer who does a lookup shouldn't have any problem loading the history and doing a reorder. And likewise in the admin, there shouldn't be an issue viewing those orders that don't have payment data. I've recently completed a project where I imported orders from an external system -- no shipping or payment data. Viewing in admin wasn't a problem and order history is also not an issue.

Scott

[Kent Multer]

I've recently completed a project where I imported orders from an external system -- no shipping or payment data. Viewing in admin wasn't a problem and order history is also not an issue.

Great, that's what I was hoping to learn. Thanks!

Stay healthy, y'all! --