CBGitty
-
Posts
39 -
Joined
-
Last visited
Posts posted by CBGitty
-
-
It looks like the issue may actually be in the order creation code, not the PayPal_Pro module... when I cehcked the CubeCart_order_summary table, the 'state' field for the failed order had the full state name instead of the ID number. So the bug appears to be in the order creation/checkout process... Though some validation in the module code to make sure valid values are being passed to PayPal sure would be a nice idea.
-
It is apparently some deeper issue... a newly-registered customer just had the problem, with her full state name being passed instead of the abbreviation.
Line 60 of /modules/plugins/PayPal_Pro/gateway.class.php may be playing a role:
$state = ($this->_basket['billing_address']['country_iso']=='US' || $this->_basket['billing_address']['country_iso']=='CA') ? $this->_basket['billing_address']['state_abbrev'] : $this->_basket['billing_address']['state'];
-
I am starting to think that it is due to artifact address issues left over from earlier upgrades. In the failed request, the state was passed as "California" and in the successful one after address edit it was passed as "CA". In the addressbook table, there are are a range of non-standard entries in the state field. I am going to try running some routines to standardize those to state codes and see if that helps.
-
I have looked in my request log and found the entry for the error returned from PayPal. The somewhat cryptic error message being displayed to the user is originating with PayPal, which explains why I could not find it in the CubeCart language files. Here is the returned data entry:
Response receivedTIMESTAMP=2013%2d01%2d11T18%3a16%3a47Z&CORRELATIONID=122e95b0c2e02&ACK=Failure&VERSION=65%2e0&BUILD=4181146&L_ERRORCODE0=10736&L_SHORTMESSAGE0=Shipping%20Address%20Invalid%20City%20State%20Postal%20Code&L_LONGMESSAGE0=A%20match%20of%20the%20Shipping%20Address%20City%2c%20State%2c%20and%20Postal%20Code%20failed%2e&L_SEVERITYCODE0=Error -
I recently upgraded to 5.1.5 and re-enabled the Paypal_Pro plugin, hoping that some of the issues I ran into last time had been sorted out.
The issue I am seeing now is with customers whose address entered in CubeCart is not technically valid according to the USPS. In these cases, two problems occur in regards to PayPal:
1) If they click the "Check out with Paypal" button, they are taken to a blank page.
2) If they instead click through the Checkout process, and then choose Paypal from the list of enabled payment methods, they briefly see a message regarding the address being rejected, and then they are taken to a Paypal error screen which mentions a bad merchant configuration/etc.
If the customer corrects his/her address to the USPS-approved version, then Paypal works as intended.
I have poked about through the likely suspects in terms of files where this check might be happening, but I can't seem to find it. Anyone know how to disable/override it?
-
Can you tell us what template you are using? I am having the same issue with a paid-for copy of the cintoxblue theme. Something with the javascript field validation.
-
As best I can tell, it had somehow cached my original info and was using that. When I tested it with a different card via a different browser, and without logging into my store, it seemed to work. As best I can tell from my testing, the only things that seem to matter are the CC number, expiration date and CVV. Selecting the right card type doesn't seem to matter, nor does entering a valid billing address.
I have set this payment method live on my $40K/month shop and disabled PayPal standard and card capture, so I have all my chips on the table. Overnight results seem promising.
-
I am running a slightly modified version of CubeCart 5.0.7, and just today I finally got PayPal Web Payments Pro working.
However, it seems like there isn't much validation of credit card information that gets entered if they choose to pay via Credit Card. While some basic validation of the credit card number checksums does seem to occur, beyond that card numbers don't get matched against card types, expiration dates don't seem to get validated, etc.
And the weirdest thing is that so long as I enter a valid CC number (for instance, from a mastercard), choose a valid credit card type (for instance, Visa), enter a properly formatted date (but not the right one) for the expiration date, mash in a random 3-digit number for the CVV, and put in wrong contact info... and somehow it goes through. The order in CubeCart will be changed to "Processing" with this in the transaction log:
"No match for AVS data. Transaction has been declined. CVV2 did not match"
Yet soon after I get a message from PayPal saying that the payment has been received and is OK to ship, the payment shows up in my PayPal account, and everything is apparently OK... except that I know it is all wrong.
I am very hesitant to make this thing live when it seems so bizarre. Does anyone have any thoughts or advice?
-
File manager is showing image files in the various subfolders I have created, but not in the root folder.
-
Hmm looks like it, I'll try again...
-
I've been wanting to do this for a while, and seeing your post made me finally get down to it. I've always hated having to scroll and click into the folder tree in my images folder to figure out what images were selected for a product. It was especially horrible back in earlier versions when it kept forgetting image selections.
I had to alter two files to make it happen: admin/skins/default/templates/products.index.php and admin/sources/products.index.inc.php. I have attached a ZIP of the changed files.
A couple of caveats:
* this is 5.0.7 code, don't use it on other versions.
* I know the HTML/layout using tables and whatnot is horribly deprecated and old-fashioned. There's a reason I stopped being a web developer and started selling stuff online. Anyone who wants to rework it to the latest standards can be my guest.
-
Hello,
Bloody hard to find, but there is a line in classes/cubecart.class.php that arbitrarily truncates the title. In version 5.0.7 it is line 114, and it looks like this:
$product['name'] = (strlen($product['name'])>42) ? substr($product['name'],0,38).'…' : $product['name'];
I commented it out and suddenly I had the full titles. You may need to alter the stylesheet that controls the product box height if you have extremely long product titles, to ensure they will fit cleanly.
-
I agree strongly. I have had to implement a couple of dozen bug fixes and tweaks to the core files just to make my live version of 5.0.3 relatively stable and usable, and it would be nice to have some idea of which (or any) of those will have to be redone after upgrade.
Amazon Checkout
in Technical Help
Posted
Is there any sort of documentation for getting the Amazon Checkout feature set up? I am trying to implement it on 5.2.7, which I upgraded in a testbed enviroment from 5.1.5. The store has been upgraded over the last several years originally from version 3 point something.
I have an Amazon seller account and I have set up the checkouts side of the account, got my various tokens and keys and IDs, put them into the Amazon Checkout plugin screen, enabled the plugin, and it shows up during checkout now.
Here is what I am experiencing:
1) Log into the store
2) add item to basket
3) view basket, click Amazon Checkout button
4) login to amazon in popup
5) popup disappears, left at View Basket screen
6) Click Checkout button
7) Taken to address entry screen with "would you like to login" button, even though I am already logged in.
8) If I log in again, I am taken back to view basket
9a) If I click the Amazon checkout button again, the process repeats
9b) If I click the standard checkout button, I am taken to the choose payment method screen where Amazon is not mentioned.
I have to say that after this much time with CubeCart, my expecations are pretty low when it comes to stuff actually working. The only reason I am even looking at the Amazon option is because an unacceptable number of customers are unable to successfully check out due to issues with the PayPal checkout process which have been mentioned in a number of other posts.