Forum Moderators: buckworks
[paypal.com...]
(That's obviously not my real ID! hehe)
I get taken to my paypal payment page and it still has the same javascript error which is caused by an extra "," at the end of the ppns.addEngines javascript array definition.
I am in the UK which may be why some people get it and some don't, perhaps if you are in the US it works ok?
I have also tried using a couple of other paypal account ID's that belong to friends just to test it and I still get the same Javascript error. I've also tried it in several browsers and several different PC's in different locations all with the same result. This is really affecting my shop sales because as soon as the customer sees a Javascript error pop up they just don't pay because they don't feel safe, my PayPal payment conversions have gone through the floor in the last couple of weeks since this problem was first noticed. Surely this must be treated as a priority by PayPal? It's affecting everyone (I the UK at least) that uses the standard PayPal checkout mode!
Regards,
David.
Can anyone with a PayPal account in the UK go to the page I posted above (substituting your own paypal email in it) and see if you get a javascript error too, you don't need to actually log in or anything. The error is on the page where you are asked to "Secure Checkout" or "Login".
Thanks.
Simon.
PayPal have to date done nothing to fix this.
Perhaps you've noticed that your PayPal sales are down, been wondering why? Well this is why! Every Customer gets a javascript error box BANG in the middle of their screen asking them if they want to continue "yes/no" when they try to pay, who would carry on after seeing that? I wouldn't for one, I'd assume that something dodgy was going on and put my credit card safely back in my wallet.
Simon.
The cart system I now have is far quicker and much more professional.
Javascript should not be used as a necessity on a website for the user to fulfil their experience. It should be for adding fluffy bits on top which help but are not essential to accomplish a task.
To quote him: "I've got as a workaround (until this gets fixed) is for you to add "Country=gb" or "country.x=gb" to the buttons or links from your website, and that should prevent your customers from seeing this error."
What I've done is add this to my PayPal submit form:
<input type=hidden name=country.x value="GB">
This seems to work for me so perhaps everyone else can try this and report back.
Simon.