Closed Bug 502924 Opened 16 years ago Closed 14 years ago

PayPal page should be opened in the users local language

Categories

(addons.mozilla.org Graveyard :: API, defect, P5)

x86
Windows XP

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 526967
4.x (triaged)

People

(Reporter: leszekz, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.9.1.1pre) Gecko/20090705 Shiretoko/3.5.1pre (.NET CLR 3.5.30729) Build Identifier: When user going to make donation on the PayPall (calling PayPall from localized AMO page e.g. 'pl'), is opened page in the English language. I think that script should send information about user domain, and PayPall should be opened in the user language. Reproducible: Always
I'm not sure there is anything we can do here. We're just sending people to paypal.com - it should be up to them to redirect to paypal.pl. I don't want to have to maintain a list of locales that paypal supports. Nick has been talking with some people at paypal recently. CCing him to see if he can get us any hints.
The paypal docs state that their site defaults to en-US unless you explicitly pick another locale. Actually, I don't recall if you can pick another locale or just a different currency code. Matching locales and currency codes would be even more fraught, if that's all they give us.
(In reply to comment #2) > The paypal docs state that their site defaults to en-US unless you explicitly > pick another locale. Actually, I don't recall if you can pick another locale > or just a different currency code. Matching locales and currency codes would > be even more fraught, if that's all they give us. If we pick a locale that they don't have, does it fall back to English? If that's the case we could just pass through what we have.
(In reply to comment #2) > The paypal docs state that their site defaults to en-US unless you explicitly > pick another locale. I seem to remember, after logging in it gives you your preferred language, though.
Summary: PayPall page should be opened in the users local language → PayPal page should be opened in the users local language
For my themes, when you click on Contribute, one frequently gets the Dutch language, which is for a lot of people unreadable...
Wil emailed Paypal to inquire about this and hasn't heard back yet.
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P5
Target Milestone: --- → 4.x (triaged)
clouserw: Did you ever hear back from PP? A user asked me today about this, and the exact problem seems to be that Paypal opens up in the *developer*'s language (that's consistent with comment 5). Example Link: https://addons.mozilla.org/en-US/firefox/addon/4891/ -- the Austrian Paypal page will open up because the add-on developer is from there.
Everything I know is in https://bugzilla.mozilla.org/show_bug.cgi?id=526967#c13 - they are kind of dupe bugs. I don't know why vimperator.org would trigger Austrian though. Also, surprise!, paypal never got back to us about the extra parameter.
Just for the record, I followed the instructions on https://bugzilla.mozilla.org/show_bug.cgi?id=526967#c13 and just have a single .org mail address registered with PayPal, and finally (after clearing cookies, just to be sure), the "Contribute" button on vimperator's page on addons.mozilla.org seems to link to the English PayPal form. So it's definitely a PayPal bug IMHO, but maybe we can circumvent somehow, as there a probably many addon developers with the same problem and not even aware of the problem.
I think there's a flag we could send to force English for everyone, though that's not spectacular by any means.
(In reply to comment #10) > I think there's a flag we could send to force English for everyone, though > that's not spectacular by any means. I agree, though I'd argue most of our clientele probably prefers being taken to the English page over a random page that they might not be able to read at all.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.