I set all the configurations for the payment method "Paypal Express checkout", but the button doesn't appear in the cart section.
Do I need some other configurations ?

Thanks

Comments

rolfo85 created an issue. See original summary.

TR’s picture

TR’s picture

Category: Bug report » Support request
Priority: Major » Normal

I can't reproduce this. The express checkout button should appear on the /cart page, but not on the /cart/checkout page.

rolfo85’s picture

If I enable the "Paypal Express Checkout" payment method, filling all the required information about the API credentials, then, the button doesn't appear anywhere. Of course, it should appear on the Cart page.

Do I need to set other configurations to get it working ?

thanks

TR’s picture

Status: Active » Postponed (maintainer needs more info)

Please see if you can reproduce this on simplytest.me, and post the url to your test site on that server if you are able to reproduce it, then I can take a look at what you've done.

rolfo85’s picture

Hi,

That's the link to reach the test site: https://mrqt7.ply.st
Username: admin
Password: admin

I created a simple product and set the payment method "Paypal Express checkout" filling my Sandbox Paypal credentials.
As you can see, there's no "Paypal checkout" button anywhere.

Thanks in advance

TR’s picture

Coincidentally I just did the same thing a few minutes ago and it worked for me - drqt8.ply.st username/password drqt8/drqt8

I'll look at your site to see what I can find, but you should look at my site too ...

Did you use Ubercart 8.x-4.x-dev ??

TR’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)

OK, I see that the problem is that you're using 8.x-4.0-alpha4, not 8.x-4.x-dev. We've done a lot of work on the payment methods. I'm not going to try to figure out exactly what changed since alpha4, but it seems to work fine in -dev for me and on simplytest.me. I'm going to assume that the problem is with alpha4.

Note you should specify the correct version when you post an issue - you chose 8.x-4.x-dev, but you should have chosen 8.x-4.0-alpha4 if that's what you were using. Then I would have said try the -dev version and it would have saved us both a lot of time.

rolfo85’s picture

Sorry a lot. I didn't realize that.
Thank you so much.

Just a question, would you maybe suggest using the dev version of Ubercart for a production site ?

I should develope a basic ecommerce site within an existing one built with D8.

Is it too much risky?

TR’s picture

I don't understand why people are reluctant to use -dev. -dev is -alpha4 plus bug fixes and plus additional features. -dev is always current with the recent changes in Drupal core. -dev is always working and always passes all the automated tests. -dev never has experimental untested code. For a production site, I would *always* use -dev and I would keep my site up-to-date as much as possible by updating to the current Drupal core version and current Ubercart -dev on a frequent basis.

rolfo85’s picture

About your wonder... That is the power of green colour.

But anyway, assuming that the stable version would be much better, in case of simple ecommerce sites, is the "DEV" current version enough stable to be used in a production site ?

Thanks in advance

TR’s picture

Well, I would say that an "alpha" version is never appropriate for a production site. -dev is always better than "alpha". And -dev is always better than a "beta" version. But an actual release should be good for a production site. The advantage of -dev over an actual release is that -dev will have bug fixes and new features. If you don't need the bug fixes or new features then you can use the actual release, otherwise -dev will always be better.

Ubercart does not yet have an 8.x-4.0 release, so -dev will always be the most functional and most bug-free version. If you run into problems with 8.x-4.0-alpha4 chances are that the problems will already have been fixed in -dev.

rolfo85’s picture

Thanks a lot for the explanation