[Plugin: eShop] Incorrect page at Paypal

Not an eShop setting, you’ll have to query Paypal abaout it.

Actually, i believe the issue is becasue eshop is passing the users email to paypal at checkout. If paypal receives the email address then they automatically populate it in the login email address, and send the user to the login screen, if no email is sent to them they send the user to the pay with credit card screen.

That said, is it necessary to pass the users email to paypal at checkout?

Well I still see this on the page:

Don’t have a PayPal account?
Use your credit card or bank account (where available). Continue

And continue is a link to the credit card form.

I know what the poster is asking though, but paypal really doesn’t like people to use the credit card because they don’t make as much money, so they try to discourage it that way…..

yes, exactly. And if the users email is not sent at check out, then the page they would land on would be the one that you get to after clicking continue.

A simple way to test it is to create a simple buy now button, and save if off as test.html or something. If you have no paypal cookies, and click the buy now button, you will be taken directly to the page to enter the credit card information. not the page with…

‘Don’t have a PayPal account?
Use your credit card or bank account (where available). Continue’

So, is it necessary to send the users email to paypal?

hmmm, if it really is as simple as that then I’ll delete the email address from the data sent over – or at least make it optional via a setting, which may be preferred.

Added to my todo list.

Well, I think it’s that simple, and I hope it is. Thanks for the update. I look forward to the next release.

Most people start their post with “Eshop is awesome” so, I think I will end with that.

Eshop is awesome! Truely, for all the plugins I have used, eshop is well polished and your support is awesome.

Thanks again.

hmmm, if it really is as simple as that then I’ll delete the email address from the data sent over – or at least make it optional via a setting, which may be preferred.

Added to my todo list.

YAY!!!!!!!!! That’s a great!

BTW, what actually chnaged in trhe latest version? I don’t want to upgrade unless its really worthwhile because I have had to make some chnages the the code for some things that were not possible to alter via CSS and I don’t want to have to redo them just yet….

use this to compare revisions:
https://plugins.trac.www.ads-software.com/log/eshop/

Thanks for the link, however, i viewed the readme that is in 3.7.2 and the changelog ends with 3.7.1

use the diff(radio buttons on left) available via that page.

ahh..gotcha. Thanks!

that’s great, but a plain english bullet list explaining what thise chnages actually mean would be a lot more helpful to a non programmer like me ??

no it wouldn’t. That page actually provides detailed differences between 2 different revisions enabling you to update manually if you iwsh to do so.

I provide a small summary within the readme for every update.

Hmmm, yes, it would.

While it is certainly handy to be able to manually update the code if I need to, as someone who doesn’t understand what most of the code does, this doesn’t help me to understand if I *need* to upgrade.

The readme does not seem to have a summary for 3.7.2, only for the previous 3.7.1 update.

I’m trying to be obtuse, but that link you provided is very overwheming and confusing, I feel like I need a manual to know how to navigate it.