• Resolved technicalx

    (@technicalx)


    Error does not happen in 2.8.2

    [25-Sep-2024 05:18:52 UTC] PHP Fatal error: Uncaught TypeError: Argument 1 passed to WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package::addModule() must implement interface WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Module\Module, instance of YWSBS_WC_PayPal_Payments_Module given, called in /home//public_html/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php on line 37 and defined in /home//public_html/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php:244
    Stack trace: 0 /home//public_html/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php(37): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package->addModule(Object(YWSBS_WC_PayPal_Payments_Module)) 1 /home//public_html/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(77): {closure}('/home//…') 2 /home//public_html/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(92): WooCommerce\PayPalCommerce\init() 3 in /home/****/public_html/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php on line 244

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Krystian from Syde

    (@inpsydekrystian)

    Hello @technicalx

    Thank you for providing this.

    It appears that the error is happening in the YITH compatibility area, so it’s most likely related to their plugin. We’ll look further into this.

    Please let us know if the problem still occurs when you disable all plugins except for PayPal Payments and WooCommerce. If the error doesn’t happen, try enabling the plugins one by one to find out which one might be causing the issue, most likely it’s YITH.

    Kind Regards,
    Krystian

    Hi,

    We’re also getting a critical error since updating to 2.9.1 this morning, so we’ve had to roll back to the previous version.

    Side note, we also have a YITH plugin installed.

    An error of type E_ERROR was caused in line 244 of the file /var/www/vhosts/example.co.uk/httpdocs/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php. Error message: Uncaught TypeError: WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package::addModule(): Argument #1 ($module) must be of type WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Module\Module, YWSBS_WC_PayPal_Payments_Module given, called in /var/www/vhosts/example.co.uk/httpdocs/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php on line 37 and defined in /var/www/vhosts/example.co.uk/httpdocs/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php:244
    Stack trace: 0 /var/www/vhosts/example.co.uk/httpdocs/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php(37): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package->addModule() 1 /var/www/vhosts/example.co.uk/httpdocs/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(77): {closure}() 2 /var/www/vhosts/example.co.uk/httpdocs/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(92): WooCommerce\PayPalCommerce\init() 3 /var/www/vhosts/example.co.uk/httpdocs/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCommerce{closure}() 4 /var/www/vhosts/example.co.uk/httpdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 5 /var/www/vhosts/example.co.uk/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action() 6 /var/www/vhosts/example.co.uk/httpdocs/wp-settings.php(555): do_action() 7 /var/www/vhosts/example.co.uk/httpdocs/wp-config.php(155): require_once(‘…’) 8 /var/www/vhosts/example.co.uk/httpdocs/wp-load.php(50): require_once(‘…’) 9 /var/www/vhosts/example.co.uk/httpdocs/wp-login.php(12): require(‘…’) 10 {main} thrown

    Plugin Support Krystian from Syde

    (@inpsydekrystian)

    Hello @technicalx & @brightcherrydesign

    Unfortunately, this issue cannot be resolved from our end. We have updated our system to use a modular framework called Modularity. However, older Dhii modules should still function the same way, so it’s unclear why there’s a clash in this case.

    We would have informed the YITH team if we had known about this issue earlier. While we’re sorry for the inconvenience, this problem will need to be reported to YITH, as they will need to address and fix it on their side.

    Let us know if you need further assistance!

    Kind Regards,
    Krystian

    Thread Starter technicalx

    (@technicalx)

    hopefully someone reports it, I did my part already.

    Plugin Support Krystian from Syde

    (@inpsydekrystian)

    Hello @technicalx

    Since we have not received any further communication from you, we are assuming that your issue has been resolved.

    Therefore, we mark this thread as resolved. If you still have any questions or if a new problem arises, don’t hesitate to open a new thread.

    Kind regards,
    Krystian

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.