• Resolved megathawt

    (@megathawt)


    Please promise that support for this will not end before proper fix to “PayPal Payments” is made.

    We moved from “PayPal Checkout” to “PayPal Payment” but now need to regress back to “PayPal Checkout” due to critical errors.

    As Inpsyde Niklas (@niklasinpsyde) has said of the new plugin versions 1.6.1 to 1.6.4:
    “We basically replaced a critical problem with a lesser one as a temporary measure until we could provide a proper fix.”

    The “lesser one” is also a critical show-stopping problem for us.

    Until there is a “proper fix” please continue to support this old plugin.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hi there,

    We still have support planned to stop on 1 Mar 2022, and updates actually already stopped about 4 months ago.

    Still, I would love to understand what exactly is happening with PayPal Payments for you that is stopping you from having the upgrade and change to the new PayPal plugin for WooCommerce. Could you share more details?

    I do see the plugin working as expected and I can’t reproduce errors, so I wonder if you actually had conflicts or something like that while using PayPal Payments.

    For now, it’s possible that WooCommerce PayPal Checkout Payment Gateway will continue working for the near future, but might no longer work properly at some point.

    Thread Starter megathawt

    (@megathawt)

    Felipe @felipea8c,

    Just check out the support page for WooCommerce PayPal Payments.
    It’s not just me having “conflicts or something like that” the support page for the plugin details the problems.

    I quoted what the problem is above but let me give more details below:

    Look at Inpsyde Niklas’s Plugin Support reply to the issue “Plugin no longer giving error messages when fields are incomplete since update” from David Robinson.

    There was a “critical problem”, Plugin Support’s own words, with 1.6.1.
    Support said “In update 1.6.2, the checkout validation behavior had to be temporarily moved to after the order creation at PayPal to prevent an issue that could cause orders to end up in a Failed order status despite a successful payment. We basically replaced a critical problem with a lesser one as a temporary measure until we could provide a proper fix.” Updates 1.6.2, 1.6.3, and 1.6.4 all contain an unacceptable workaround as follows:

    The workaround is also a critical problem — the modal popup for the PayPal payment pops up BEFORE the form is validated. The user fills out their payment info and THEN the form is validated. If there are errors, the user corrects the errors and then has to go back to trigger the modal popup AGAIN. The current checkout validation order would be too confusing and annoying for customers because we have a large, customized form that may take a few tries to pass all validations.

    According to support there is not yet a “proper fix”.

    It’s not just me who saying it isn’t working Plugin Support has accepted this as a problem and cannot commit to when it will be properly addressed.

    Hi there @megathawt,

    Thank you for the additional information.
    As Niklas details in their reply here, a fix for that checkout validation issue is expected to be released in February 2022.

    While I cannot comment on the effect any ongoing issues would have on the date when support for PayPal Checkout will end, I can certainly understand wanting to wait until those issues are fully resolved before making the switch.

    I recommend staying tuned to that ongoing thread for future updates. If there are critical bugs preventing folks from upgrading to PayPal Payments as we draw nearer to the time of the planned ending for support of PayPal Checkout, please feel free to reach back out with any concerns.

    Thanks,

    Thread Starter megathawt

    (@megathawt)

    My concern is that I see support running right up to line that says “Support for PayPal Checkout will not be ended before it’s replacement, PayPal Payments, is production ready.” but yet not stepping across it.”

    I’m just saying “Please commit to supporting PayPal Checkout until it’s replacement is production worthy”.

    Right now I’m being asked to upgrade to this:

    Woo Commerce PayPal Payments reviews
    5 stars — 17
    4 stars — 4
    3 stars — 2
    2 stars — 3
    1 star — 113

    It’s not working for us due to show-stopping bugs! I need to go live and know that I have a support commitment, that’s all.

    I’m just sayin’ — PLEASE! Fix the new thing before dropping support for the old, working thing!

    Plugin Support Sol J. a11n

    (@solstudioim)

    Hi @megathawt

    I’m just sayin’ — PLEASE! Fix the new thing before dropping support for the old, working thing!

    I understand that completely!

    For now, I would say that we would need to wait for the final fix which is roughly coming in the second half of February as per Niklas said, from PayPal Payments support.

    Have a great rest of your day!

    The PayPal Payments plugin is HORRENDOUS to set up. I have read the documentation until I’m cross-eyed. I created the manual credentials (Live Client ID, Live Secret Key) for woocommerce. The client’s paypal account has been set up for A YEAR, and worked flawlessly with paypal checkout plugin. I AM ON THE HUNT FOR SOMETHING DIFFERENT. THE BACKEND WON’T AUTHORIZE, MISSING TOKEN, ALL KINDS OF ISSUES!

    Plugin Support nathvi V. a11n

    (@nathvi)

    Hi @ideahost

    Thanks for your message.

    I’m sorry to read you are having a problem with PayPal Payments, to help you resolve the problems you are having could you open a new support thread so we can help you get this sorted?

    Please include any error messages you are getting and your System Status Report: you can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”. Once you’ve done that, you can paste it in the thread.

    This will allow us to better understand what is occurring and keep things tidy and organized to address any problem individually.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Please don’t end support before critical problems with new plugin are fixed.’ is closed to new replies.