Closed (won't fix)
Project:
Payment
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
3 Jun 2016 at 14:29 UTC
Updated:
8 Jun 2016 at 09:42 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
jagermonster commentedHere is a patch that adds a new payment method for purchase order payment processing.
Comment #3
jagermonster commentedThere was a bug on the edit payment page that was not including the purchase order number when editing the payment. here is the fix
Comment #4
jagermonster commentedApply both patches, first #2 then patch #3
Comment #5
xanoThank you for this submission! With software projects, new features are added to the latest major version first, which in this case means 8.x-2.x-dev, so as never to cause regressions (features being available in older versions, but not in newer versions).
Can you explain the use cases of this payment method, and why it should be added to Payment instead of being published in a third-party module?
Comment #6
jagermonster commentedIts a very simple module that only adds a textfield that allows the user making the purchase to supply a purchase order number. Since it is so simple i thought it should be part of this module. Generally payment systems does allow for a purchase order payment method, this is why i included it here
Comment #7
xanoThanks for the explanation. This is a bit too specific for Payment itself; the existing payment method serves a combined role of being useful for testing, demos, and some real-life scenarios, but this one does not add much value. On top of that anything will need to be added to 8.x-2.x-dev first.
I recommend you create a small third-party project for this. Writing a payment method plugin for Payment 8.x-2.x-dev is easier than a controller for 7.x-1.x-dev, so in terms of maintenance you won't have to expect too high a load.