Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
1414 posts
|
So was there a bug? If so, what should we do to fix it?
Vinay Agarwal wrote: David, You are right. No change will be made to this function. Vinay -----Original Message----- From: [hidden email] [[hidden email]] On Behalf Of David E. Jones Sent: Wednesday, April 12, 2006 3:16 PM To: OFBiz Users / Usage Discussion Subject: Re: [OFBiz] Users - Ecommerce: Using BillingAccountfor checkoutreturns "Please select a method of payment" This isn't quite correct. Other payment types can have an amount associated, and in fact for payments split among various payment methods this is necessary. If you aren't seeing these options then it is probably because you are looking at the one-page checkout screen. It doesn't have some of the details that are on the split out payment screen, for example. -David Vinay Agarwal wrote:Si, Well, the amount should be replaced with null since it is null for all payment types as far as I can tell. No payment type, except for billing account, has amount string, therefore, amount is null for them. For billing account, it's looking at amount_EXT_BILLACT field which is also null. Vinay -----Original Message----- *From:* [hidden email] [[hidden email]] *On Behalf Of *Si Chen *Sent:* Wednesday, April 12, 2006 2:07 PM *<a class="moz-txt-link-freetext" href="To:*">To:* OFBiz Users / Usage Discussion *Subject:* Re: [OFBiz] Users - Ecommerce: Using BillingAccountfor checkoutreturns "Please select a method of payment" Are you sure? Where would amount come from? Vinay Agarwal wrote: Si, On second thought, we should simply delete the stuff to get amount and change this ---------------- String amountStr = request.getParameter("amount_" + paymentMethods[i]); } Double amount = null; if (amountStr != null && amountStr.length() > 0 && !"REMAINING".equals(amountStr)) { try { amount = new Double(formatter.parse(amountStr).doubleValue()); } catch (ParseException e) { Debug.logError(e, module); errMsg = UtilProperties.getMessage(resource, "checkevents.invalid_amount_set_for_payment_method", (cart != null ? cart.getLocale() : Locale.getDefault())); request.setAttribute("_ERROR_MESSAGE_", errMsg); return null; } } if (amount != null) selectedPaymentMethods.put(paymentMethods[i], amount); ------------------ to ------------------ selectedPaymentMethods.put(paymentMethods[i], amount); ------------------- Vinay -----Original Message----- From: [hidden email] [hidden email] ... [show rest of quote]
_______________________________________________ Users mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/users |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
368 posts
|
Part of the problem I observed was caused by the “if (amount != null)” change. For single page checkout, no change is needed. I haven’t looked at the multi-page checkout with split payments whether the following change is needed or not. Vinay
String amountStr = null; if ("EXT_BILLACT".equals(paymentMethods[i])) { amountStr = request.getParameter("amount_" + request.getParameter("billingAccountId")); } else { amountStr = request.getParameter("amount_" + paymentMethods[i]); }
_______________________________________________ Users mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/users |
Free forum by Nabble | Edit this page |