• Resolved eselmarvin

    (@eselmarvin)


    Hi,
    after updating to 2.0.0 I have issues with PayPal-payment. When I click the yellow PayPal-button the PayPal login does not appear. Instead I get the notification:
    “Something went wrong. Please try again or choose another payment source.
    This happens sometimes, not always. Sometimes it happens on the Cart, sometimes on the Checkout. I would be grateful for any help.

Viewing 12 replies - 1 through 12 (of 12 total)
  • supaiku

    (@supaiku)

    also seeing the same error on 2.0.0

    supaiku

    (@supaiku)

    fixed by rolling back to the previous version. webhook simulations still fail though.

    Thread Starter eselmarvin

    (@eselmarvin)

    Hi @supaiku, thanks for your reply. This is only on my staging site. So I will wait for the next update.

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @eselmarvin,

    I gave it a try on your staging site with version 2.0, and it looks like the WooCommerce payment process gets stuck after confirming the payment in the PayPal popup window.
    The actual payment appears to be completed, but WooCommerce does not recognize it and won’t clear the cart.
    I recommend performing a full conflict test to rule out eventual issues with the theme or a different plugin. We recommend temporarily activating the default theme Storefront and disabling all other plugins except for?WooCommerce and?PayPal Payments to see if the behavior persists.

    Here’s a guide that explains the steps in more detail: How to test for conflicts
    Please let us know how this works out for you.

    @supaiku Something went wrong. Please try again or choose another payment source. is a generic error and can have various different causes.
    I suggest following the steps above for conflict testing and creating a new thread for yourself with a copy of your system report and any new findings after performing the test.
    Thanks!

    Kind regards,
    Niklas

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    @eselmarvin Small correction, after sending out the message above, the latest payment attempt (order 1834) cleared after it loaded for a little while. it probably two or three minutes to complete. So it did eventually complete, but was quite slow.
    It would still be good to check if the behavior persists with only PayPal Payments and WooCommerce active.
    Thanks!

    wildflower24

    (@wildflower24)

    Same problem here!
    This is the error report im getting

    CRITICAL Uncaught TypeError: Argument 2 passed to WooCommerce\PayPalCommerce\WcGateway\Gateway\OXXO\OXXO::WooCommerce\PayPalCommerce\WcGateway\Gateway\OXXO\{closure}() must be of the type bool, null given, called in /home/dbname/domains/domainname/public_html/wp-includes/class-wp-hook.php on line 310 and defined in /home/dbname/domains/domainname/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Gateway/OXXO/OXXO.php:108`

    Only solution working for now is rollback plugin to previous version.

    alexliii

    (@alexliii)

    Exactly same issue here “Something went wrong. Please try again or choose another payment source.”

    Thread Starter eselmarvin

    (@eselmarvin)

    Hi @niklasinpsyde ,
    thanks for your reply. I have just done a test as described on the site you linked. It seems to me that there is a conflict with the plugin “Germanized for Woocommerce”. Payment was completed but it took several minutes. This is only on my staging site, so it is not a big problem for me. But it would be great, if you could fix this issue in the next updates. Thanks!

    Thread Starter eselmarvin

    (@eselmarvin)

    Hi @niklasinpsyde,

    I just updated Germanized to 3.11.2. The changelog said “Fix: Prevent errors caused by WooCommerce PayPal Payments from processing shipments”. Unfortunately the issue is still there. When I click the PayPal button on the cart the payment process takes really long. When I click the PayPal button on the checkout I get the notification “Something went wrong. Please try again or choose another payment source.”

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @eselmarvin,

    Sorry about that compatibility problem with the Germanized integration in PayPal Payments. This was fixed in the last update 2.0.1 and should now be working as expected.
    Please let us know if any issues persist for you with this update. Thanks!

    Kind regards,
    Niklas

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    We have not heard back from you in a while, and the latest version came with relevant compatibility improvements, so I’m marking this thread as resolved.
    If you have any further questions, please feel free to reopen this topic or create a new one. Thanks!

    Hello,
    I am also getting an error message. Not sure what to do about it:
    An error of type E_ERROR was caused in line 156 of the file /home/customer/www/startcrochet.com/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Gateway/OXXO/OXXO.php. Error message: Uncaught TypeError: Argument 1 passed to WooCommerce\PayPalCommerce\WcGateway\Gateway\OXXO\OXXO::WooCommerce\PayPalCommerce\WcGateway\Gateway\OXXO\{closure}() must be of the type string, null given, called in /home/customer/www/startcrochet.com/public_html/wp-includes/class-wp-hook.php?on line 310 and defined in /home/customer/www/startcrochet.com/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Gateway/OXXO/OXXO.php:156
    Stack trace:
    #0 /home/customer/www/startcrochet.com/public_html/wp-includes/class-wp-hook.php(310): WooCommerce\PayPalCommerce\WcGateway\Gateway\OXXO\OXXO->WooCommerce\PayPalCommerce\WcGateway\Gateway\OXXO\{closure}(NULL)
    #1 /home/customer/www/startcrochet.com/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
    #2 /home/customer/www/startcrochet.com/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #3 /home/customer/www/startcrochet.com/public_html/wp-admin/includes/meta-boxes.php(1599): do_action(‘add_meta

    Would appreciate some advice.
    Thank you!
    May

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Error after update to 2.0.0’ is closed to new replies.