• Resolved Davood Denavi

    (@binarywc)


    On Friday I received this email from a client:

    I’ve seen a rash of “Failed Orders” since the last time I updated, August 17. I am seeing frequent “Failed Order” receipt showing that the customer tired to pay with a credit card. For some of them, I then see a few minutes later, the successful order paid through PayPal. In the Back End, WooCommerce > Orders, I see this message when examining the order:

    “Could not retrieve order. /home/customer/www/mechanicalelements.com/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-api-client/src/Endpoint/OrderEndpoint.php:459 Order status changed from Pending payment to Failed.”

    I normally see a failed order once or twice a year. All of the sudden it’s once or twice a day. Something happened because of the update. What did Woo do?

    I can’t tell if the issue is with WooCommerce core (Version 6.8.2), or with the PayPal Payments Plugin (Version 1.9.2).

    After looking at their website I found that the Credit Card field which we’ve had activated for a few months was missing and it looked like orders were going through when users used the Smart Buttons mentioned in this thread.

    So, I added the following CSS to our child theme:

    .payment_method_ppcp-credit-card-gateway {
        display: contents !important;
    }

    When the next order came in we went were still getting the same error that was mentioned in that thread. However, that buyer immediately clicked the smart button and the order came through correctly.

    So, we mutually decided to implement the work around mentioned in the thread I linked to above and also deactivated SG Optimizer plugin since we are on SiteGround. That seems to have fixed the issue. However, we believe that the problem we were having was related to updating from 1.7.x (or 1.8.0) to 1.9.2. Meaning that the problem we were having has existed since 1.9.0 was released on July 4, 2022.

    Is there a fix that would allow us to upgrade back to 1.9.2 from the script fix workaround?

    • This topic was modified 2 years, 2 months ago by Davood Denavi.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Syde Joost

    (@joostvandevijver)

    Hello @binarywc

    thank you for reaching out to us, we are currently testing this fix, but have already made a beta version available. So far we had some positive responses back on this beta version, so we are fairly positive about it. We can’t guarantee that there are no issues included until we get the test results back from QA & PayPal, but I think it would be good enough for a live environment while keeping a close eye on the orders until the official release is done within 2 weeks.

    You can download the beta release here: https://github.com/woocommerce/woocommerce-paypal-payments/releases/tag/1.9.3-rc2

    Please let me know if you have any more questions for us or feedback on the beta release.

    Kind regards,
    Joost

    Thread Starter Davood Denavi

    (@binarywc)

    Thank you for the quick reply!

    Are you suggesting that we use the RC2 you linked us to? If so, I do not think the client will be comfortable doing that. Which leads me to these two questions.

    Will sticking with the workaround from that other thread potentially break any functionality that we have not yet seen problems with of the WooCommerce PayPal payments plugin?

    Do you know if activating SG Optimizer again will stop the workaround from working?

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @binarywc,

    The problem was only introduced in the latest update 1.9.2. The regular 1.9.1 version (including the one labeled “scriptfix”) should be working fine.
    The linked 1.9.3-rc2 version is expected to be released any day as an official update.
    Regarding the SiteGround Optimizer compatibility, there shouldn’t be any major differences between 1.9.1, 1.9.2 with the workaround filter, or the 1.9.3 version without the filter (is already included in the plugin then).
    We are looking into improving the overall compatibility though, as the latest versions (1.9.2+) do not provide the same compatibility with older browsers compared to previous plugin versions.

    Kind regards,
    Niklas

    Thread Starter Davood Denavi

    (@binarywc)

    Once again, thank you for the fast reply.

    I am considering this thread resolved for now… I will tag the thread as resolved in a few days after we have reactivated the SG Optimizer plugin and confirmed that it is all working as we want it to again and then start a new thread if there are further problems after the 1.9.3 update is released!

    Plugin Support Syde Joost

    (@joostvandevijver)

    Hello @binarywc

    Thank you for your response. I will mark this as resolved and indeed, please open a new thread if 1.9.3 does not resolve the issue for you, if you encounter any other issue or simply have a question.

    Kind regards,
    Joost

    Thread Starter Davood Denavi

    (@binarywc)

    It is not resolved until we get a few more orders with the SG Optimizer plugin enabled again and there are no problems. I have tagged it as not resolved while we wait for a few more orders.

    Thread Starter Davood Denavi

    (@binarywc)

    The CC field is working correctly with the 1.9.1 script fix and SG Optimizer plugin activated. If we have any further issues we will start a new thread when 1.9.3 is released.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘CC Field Missing’ is closed to new replies.