PHP Fatal Error on v2.2.1

  • Resolved nimonogi

    (@nimonogi)


    1 year, 3 months ago

    [27-Aug-2023 17:39:53 UTC] PHP Fatal error: Uncaught TypeError: WooCommerce\PayPalCommerce\Subscription\SubscriptionModule::WooCommerce\PayPalCommerce\Subscription{closure}(): Argument #2 ($post) must be of type WP_Post, WP_Comment given, called in /usr/www/users/user/wp-includes/class-wp-hook.php on line 310 and defined in /usr/www/users/user/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-subscription/src/SubscriptionModule.php:230
    Stack trace: 0 /usr/www/users/user/wp-includes/class-wp-hook.php(310): WooCommerce\PayPalCommerce\Subscription\SubscriptionModule->WooCommerce\PayPalCommerce\Subscription{closure}() 1 /usr/www/users/user/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters() 2 /usr/www/users/user/wp-includes/plugin.php(517): WP_Hook->do_action() 3 /usr/www/users/user/wp-admin/edit-form-comment.php(257): do_action() 4 /usr/www/users/user/wp-admin/comment.php(92): require(‘/usr/www/users/…’) 5 {main}

    thrown in /usr/www/users/user/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-subscription/src/SubscriptionModule.php on line 230

Viewing 8 replies - 1 through 8 (of 8 total)

  • Same for me when I go to edit order page.

    Looks like 2.2.1 broke HPOS.

    I was running with HPOS enabled, on staging site as well as main site. Switched back to old-style and it works as expected.

    Thread Starter nimonogi

    (@nimonogi)

    I am not sure that this is the case. Here are my HPOS setting: https://ibb.co/6Nh6s2v

    I switched back to using the WordPress posts table instead of HPOS and everything went back to normal as well.

    Hi,

    I just updated a site and am now seeing the same error. In our case, it’s disabling the admin pages added by our hosting provider to interact with their cache, etc. Would be great to see a fix for this ASAP.

    Thanks!

    Plugin Support Syde Joost

    (@joostvandevijver)

    Hello all,

    We are aware of this issue that was caused by our last release and got a fix for it from our developers. We created a package for you that you can download here:
    https://drive.google.com/uc?export=download&id=16GC-69a1JmA65HH0GIj4xOAQNL313hDP

    We think we will try to release this as soon as possible as version 2.2.2, but we are still discussion this. For now, you should be able to use this package as a temporary fix until we do a next release. Any details on this issue/fix you can find on our GitHub issue here.

    Kind regards,
    Joost

    Thanks @joostvandevijver. I just updated to the patch release and our issue appears to have been resolved. Appreciate the quick turnaround on this one.

    Cheers,
    Phil

    Plugin Support Syde Joost

    (@joostvandevijver)

    Hello @philkurth

    Thank you for confirming this fix. As said, we are trying to get a quick release in place to correct this, but for now we at least have a temporary fix in place. Since there is not much more we (from support) can do, we will mark this thread as resolved.

    Kind regards,
    Joost

    Is thist fixed in 6.3.1?

    Kind Regards
    Benjamin

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘PHP Fatal Error on v2.2.1’ is closed to new replies.