Rank: Member
Joined: 10/10/2007(UTC) Posts: 5
|
I did a search to try and find this, so if I missed it somewhere I apologize. The payment control does not respect the "Require PO number when Purchase Order is selected" configuration option. It seems to me that this is probably the only function of this checkbox, so I'm curious if I missed some other spot where it's having an effect. The checkbox does set the WebAppSettings value. I fixed it by modifying /BVModules/Controls/Payment.ascx.bv. In the IsValid method I changed the code that reads: Code: If Me.rbPurchaseOrder.Checked = True Then If String.IsNullOrEmpty(Me.PurchaseOrderField.Text) Then paymentFound = False result = False Me.Errors.Add("Purchase order number required.")
to this: Code: If Me.rbPurchaseOrder.Checked = True Then If String.IsNullOrEmpty(Me.PurchaseOrderField.Text) And WebAppSettings.PaymentPurchaseOrderRequirePONumber Then paymentFound = False result = False Me.Errors.Add("Purchase order number required.")
Seems to work fine.
|
|
|
|
Rank: Member
Joined: 3/3/2006(UTC) Posts: 1,737
|
I just tested this on my site and I got the "Purchase order number required." message loud and clear.
Sp3.2, one page checkout. |
Optimists invent airplanes, Pessimists buy parachutes. |
|
|
|
Rank: Member
Joined: 10/10/2007(UTC) Posts: 5
|
I'm sorry... I should have explained better. It ALWAYS requires it. If you uncheck the box it still requires the purchase order number.
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.