WP Junky

Unfortunately no. That just tells me how to set things up. I have the plugin correctly set up. Apparently I’m not explaining this well. I’ll give it one more try:

With “Standard PayPal Checkout” once the customer clicks to check out they go to PayPal. Within PayPal’s checkout flow they see a “Pay Now” button. This is correct. The customer is paying now. They see this on the button text. They know they’ll be charged when they click or tap it. Everything is fine.

Using “PayPal Smart Checkout” with the plugin: The customer clicks to checkout in the cart. They’re transferred to PayPal for payment. Once there, they see a “Continue” button. The PayPal button is labeled “Continue”. The text below the button tells buyers they’ll be able to review the order before purchase. They can’t. Customers believe if they click/tap “Continue” they’ll be taken to another screen to verify final details before clicking to complete the purchase. That’s what is supposed to happen. however, if they click the continue button the order is completed and they’re charged immediately.

Unfortunately the way the plugin is set up, it results in PayPal displaying the “Continue” button instead of the “Pay Now” button it should probably actually be showing.

Essentially when using the Smart Checkout option, the plugin should be telling PayPal to use the “Pay Now” checkout flow and NOT the “Continue”. The way it currently does things is misleading and leads to the occasional angry customer. They’re charged when they’re told they aren’t going to be yet. When clicking continue the customer should be sent back to the merchant site or another page to finish the transaction. They shouldn’t be charged immediately and dumped to the return URL.

Basically for smart checkout the plugin should probably be using the commit:true parameter to use the Pay Now checkout flow:

paypal.Button.render({
  commit: true
});

Additional Details here: https://developer.paypal.com/docs/archive/checkout/how-to/customize-flow/#implement-the-pay-now-checkout-flow

Of course I may be missing something but at the very least, when using “smart checkout” the plugin should give sellers the option to chose whether they want to use “Pay Now” or the somewhat misleading “Continue” checkout flow.

• This reply was modified 4 years, 5 months ago by WP Junky.

Updated and coupons seem to work as intended with Smart Checkout. Thanks for the fix!

I’m still getting this error message:

INVALID_CURRENCY_AMOUNT_FORMAT line: 1, column: 63

Not having any luck with this other than it appears to be related to PayPal Smart Checkout only. Transactions with coupons will NOT process. They’ll go through ok with standard checkout. When attempting to checkout with PayPal Smart Checkout when a coupon is applied I get the error message above.

Hi there,
No custom input fields.

Retested today in an attempt to narrow it down further. Seems to be related to PayPal
Smart Checkout.

If I use Standard PayPal Checkout exclusively, transactions with a coupon code will go through just fine.

Coupons cause the aforementioned error with PayPal Smart Checkout active. I get the error message with Smart Checkout and with Smart Checkout with Standard Checkout disabled.

With Smart Checkout enabled the cart will accept the coupon and calculate the total correctly. However, when I click the PayPal or PayPal Credit Button to begin checkout, it will fail to transfer to PayPal and I get the error message above.

Here are the settings I have for Smart Checkout:

Smart Checkout Enabled
Size: Responsive
Colr: Gold Buttons
Shape: Rectangular
Layout: Vertical
Payment Methods: PayPal Credit
Disable Standard PayPal Checkout: box is checked to disable

Thanks for the respone bcworkz! I’ve tried your suggestion but couldn’t get it to work.

I’ve poked around the source code for my site and the theme appears to be calling gravatar.com from the featured post meta entry but only in the “magazine” layout of the theme. This theme has a magazine layout with magazine boxes that display on a featured image, post title, post excerpt and then at the bottom of the box for each post is meta info displaying post author, date, gravatar etc.

Here’s a section of the source code that appears to be the culprit. I’ve redacted site URLS etc.

<span
class="comments-link alignright"><a
href="http://www.ThePostURLGoesHere/#respond">0</a> </span> <footer
class="entry-meta clearfix"><div
class="alignleft"> <img
src="#" class="avatar" data-gravatar-hash='77104ef58b1eaa0da6d117adf3a4218e?s=24'/> <a
href="http://www.ThePostAuthorURLGoesHere/"
rel="author"> <span
class="meta-nav">POSTAUTHORNAME</span> </a> on
October 29, 2015</div><div
class="clear"></div></footer></div> </article>

I’ve tried fixing this via CSS but it doesn’t appear to work.
If I use
.mag1 .entry-meta{display:none}
it successfully removes the post author, date of publication and the avatar area from the page. They’re all hidden now. . . but the site still calls Gravatar.com even after clearing all caches.

I’ve also tried using the above along with

.mag1 .entry-meta .avatar {display:none}

and I’ve also tried just

.mag1 .avatar {display:none}

The site still calls Gravatar.com and the references to avatar still remain in my source code when I clear all caches.

I’m poking around trying to figure just where the magazine layout template source code is but I’m not having much luck.

I’m guessing this will end up being a “can’t see the forest for the trees” issue since I’ve been staring at code for far too long now. Any ideas or suggestions are greatly appreciated. I’ve put in a support ticket with the theme developer but it’s been a couple days with no response. At this point I want to conquer the issue and move on!

Thanks so much for the quick reply. Looks like this fixed the issue beautifully! Thanks again!

I’m not sure what they mean by “Curls” I’m assuming cURL SSL?
Is there any code I can easily add to the plug in files to tell it to NOT use cURL but “cURLS” instead?

Thanks!

Can someone please help me with this? Basically it appears to be an issue with my shared hosting provider (Lunarpages) and facebook. My hosting support took over 3 weeks to get back to me and this is finally what they replied with:

1. Sorry for the inconvenience you are experiencing. We have had this issue investigated and found that there is broken network between your server and Facebook network due to which plugin is not working properly and throwing errors. Unfortunately the issue was visible on Facebook network so there is nothing much we can do but we have contacted Facebook support to correct this issue as soon as possible. As to verify this, please check the traceroute result given below.

2. Multiple canned responses saying they are waiting for facebook to look into the issue

3. Several other useless suggestions they found in wordpress forums that had nothing to do with the issue.

And Finally and most importantly:
4.

On a deep investigation we were able to locate the issue. Curl was actually disabled by EasyApache and Curls is working fine. The plugin script has to be modified according to use Curls instead of curl. Hope now you have a hint to contact the plugin vendor to modify plugin for normal functioning on our servers.