Zen Cart Logo
Forums / Upgrading from 1.3.x to 1.3.9 / Is the paypal web alias issue fixed in 1.3.8?

Is the paypal web alias issue fixed in 1.3.8?

Locked

Views: 1,389

Results 1 to 2 of 2
This thread is locked. New replies are disabled.
04 Dec 2007, 21:45
#1
gibbro avatar

gibbro

New Zenner

Join Date:
Apr 2007
Posts:
1
Plugin Contributions:
0

Is the paypal web alias issue fixed in 1.3.8?

Hi,

My site has an issue that if the domain name is configured to web alias and hence keeps the www.myname in the main http address area no matter where you are within the site then PayPal does not work as it does not like the "myname" reference going through to it and not the full code tree path of the page that links into PayPal, so when you log into PayPal to pay it all goes pear shaped.

I found a fix for this within this forum that told me not to use web alias but to use web forwarding in my domain name configuration. This works fine but is not ideal as it confuses a lot of people as well as search engines as the full code tree path appears in the http area and not the site name. You would be amazed how many people have phoned up and told me that the site is not working because of this...

Does 1.3.8 fix this issue or is there anything else I should be doing?
(I am currently on 1.3.7)

Many thanks in advance :smile:

Rob

04 Dec 2007, 22:02
#2
drbyte avatar

drbyte

Sensei

Join Date:
Jan 2004
Posts:
63,513
Plugin Contributions:
177

Re: Is the paypal web alias issue fixed in 1.3.8?

First, let's be clear ... the so-called "paypal web alias issue" is NOT a Zen Cart issue.
It's a web design issue with how you've designed your site.
URL masking, web forwarding, web aliases, using frames, and so on are not generally wise practice anyway.

As to the "paypal web alias issue" you mention ... it's a security measure implemented by PayPal. PayPal prohibits URL masking or the use of frames etc for accessing their pages, primarily to prevent spoofing and fraud.

If you want to let them know how much trouble it's causing you and your customers, feel free to report the problem to their tech support department. I doubt they'll change their security practice though.