[ic] PaypalExpress module - billing address

Gert van der Spoel gert at 3edge.com
Mon Jan 11 19:33:42 UTC 2010

> -----Original Message-----
> From: interchange-users-bounces at icdevgroup.org [mailto:interchange-
> users-bounces at icdevgroup.org] On Behalf Of Ton Verhagen
> Sent: Monday, January 11, 2010 8:53 PM
> To: interchange-users at icdevgroup.org
> Subject: Re: [ic] PaypalExpress module - billing address
> Quoting Stefan Hornburg (Racke) wrote:
> > Ton Verhagen wrote:
> >> Dear All,
> >> We are using the PaypalExpress.pm payment module with a good rate of
> success.
> >> However, frequently the returned billing addresses from Paypal look
> awkward.
> >> Example of returned data:
> >> Rita Schlüter
> >> Königstraße 29
> >> This seems to be the case when the customer has used German
> characters like umlauts etc. in the data of his Paypal account.
> >> Any solution besides disabling the pp_use_billing_address option of
> the PaypalExpress module?
> >
> > Please tell us your Interchange version and UTF-8 settings. Paypal
> supposedly returns
> > UTF-8 text.
> Interchange version 5.7.1
> No utf-8 set
> The returned data messes up the invoice when printed.
> Need a solution where the returned data (billing address is stored in
> userdb after payment has been made when pp_use_billing_address has been
> set to 1), shows properly on the invoice.

* This is something you have noticed in 5.7.1 and it did not exist in a previous version?
* I suppose your database is latin1 not UTF8?

You will have to convince the part that outputs the data from the database that it deals with UTF8 data.
Or in this case you could perhaps still get away with converting the UTF8 to ISO8859-1 ... But I would not recommend that.

If the process is not totally automatic you can also save the data in a txt file and open with Word or something and let it convert to UTF8 before printing .. Then you do not have to touch Interchange for the one off issue ... 

If you feel lucky you can switch the UTF8 flags on but I do expect that needs database conversion etc ... I'd first upgrade to 5.7.4 in that case though as that has some more fixes in the UTF8 area I believe.



More information about the interchange-users mailing list