Technical issue after upgrade to 2.3.1

  • Resolved estebandido

    (@estebandido)


    1 year, 6 months ago

    Hello after upgrading to the version 2.3.1 I am not able to create any order on my site

    WordPress versión 6.3.1
    Tema activo: Futurio Child (versión 1.2.18.1669483004)
    Plugin actual: WooCommerce PayPal Payments (versión 2.3.1)
    PHP versión 8.0.30 Detalles del error

    Se ha producido un error del tipo E_ERROR en la línea 660 del archivo /var/www/vhosts/mysite.com/httpdocs/app/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-subscription/src/SubscriptionModule.php. Mensaje de error: Uncaught TypeError: WooCommerce\PayPalCommerce\Subscription\SubscriptionModule::WooCommerce\PayPalCommerce\Subscription{closure}(): Return value must be of type array, null returned in /var/www/vhosts/mysite.com/httpdocs/app/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-subscription/src/SubscriptionModule.php:660
    Stack trace: 0 /var/www/vhosts/mysite.com/httpdocs/app/wp-includes/class-wp-hook.php(310): WooCommerce\PayPalCommerce\Subscription\SubscriptionModule->WooCommerce\PayPalCommerce\Subscription{closure}() 1 /var/www/vhosts/mysite.com/httpdocs/app/wp-includes/plugin.php(205): WP_Hook->apply_filters() 2 /var/www/vhosts/mysite.com/httpdocs/app/wp-content/plugins/woocommerce/includes/admin/meta-boxes/class-wc-meta-box-order-actions.php(217): apply_filters() 3 /var/www/vhosts/mysite.com/httpdocs/app/wp-content/plugins/woocommerce/includes/admin/meta-boxes/class-wc-meta-box-order-actions.php(35): WC_Meta_Box_Order_Actions::get_available_order_actions_for_order() 4 /var/www/vhosts/mysite.com/httpdocs/app/wp-admin/includes/template.php(1443): WC_Meta_Box_Order_Actions::output() 5 /var/www/vhosts/mysite.com/httpdocs/app/wp-admin/edit-form-advanced.php(681): do_meta_boxes() 6 /var/www/vhosts/mysite.com/httpdocs/app/wp-admin/post-new.php(75): require(‘…’) 7 {main}

    thrown

    Have replaced my site’s name with mysite.com

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hello @estebandido

    Apologies for the trouble after the update! Are you seeing this error after manually creating an order? Can you please give it a try with this test version to see if this works for you? We haven’t been able to reproduce the error yet, so feedback would be highly appreciated.

    Alternatively, you could downgrade to the previous version 2.2.2, until a verified fix is available. I hope this helps!

    Kind regards,
    Niklas

    Thread Starter estebandido

    (@estebandido)

    Hello @niklasinpsyde

    I have just tried the test version, but it is the same. When you go to create an order manually all the fields of the order page disappear , so I can not create the order manually.

    I have just downgraded to the version 2.2.2 and it works again.

    Hope to see any fix in the future soon

    thanks in advance

    Esteban

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    Thank you for the feedback, Esteban.

    It’s possible that another plugin on your site hooks into the woocommerce_order_actions filter and doesn’t return the $actions. In the part of the PayPal Payments code where the error occurs, PayPal Payments expects to handle the WooCommerce order actions. But they are empty (null), which should never happen in a regular WooCommerce setup.
    So it’s likely that the problem does not occur when only WooCommerce and PayPal Payments are active. One option to verify this without disabling anything on your site is using the Health Check & Troubleshooting plugin and following the troubleshooting steps described here.

    We will let you know when a new version with a proper fix for the reported issue is available. It will certainly be resolved with the next update sometime in October.

    Kind regards,
    Niklas

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    This error should no longer occur in PayPal Payments version 2.4.0 and newer. Since we haven’t heard back from you in a while, I’ll mark this thread as resolved.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Technical issue after upgrade to 2.3.1’ is closed to new replies.