WooCommerce PayPal Payments Version 2.9.1 Fatal Error

  • Resolved lukeatsayhellotowoo

    (@lukeatsayhellotowoo)


    6 months ago

    After upate to 2.9.1 site crashes with fatal error.

    An error of type?E_ERROR?was caused in line?701?of the file?/home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php. Error message:?Uncaught Exception@anonymous/home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Container/ReadOnlyContainer.php:90$1f: Service with ID paylater-configurator.is-available not found. in /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Container/ReadOnlyContainer.php:90 Stack trace: #0 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/services.php(1789): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Container\ReadOnlyContainer->get('paylater-config...') #1 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Container/ReadOnlyContainer.php(71): WooCommerce\PayPalCommerce\WcGateway\WCGatewayModule::WooCommerce\PayPalCommerce\WcGateway\{closure}(Object(WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Container\ReadOnlyContainer)) #2 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/services.php(1807): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Container\ReadOnlyContainer->get('wcgateway.setti...') #3 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Container/ReadOnlyContainer.php(71): WooCommerce\PayPalCommerce\WcGateway\WCGatewayModule::WooCommerce\PayPalCommerce\WcGateway\{closure}(Object(WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Container\ReadOnlyContainer)) #4 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/WCGatewayModule.php(845): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Container\ReadOnlyContainer->get('wcgateway.setti...') #5 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/WCGatewayModule.php(91): WooCommerce\PayPalCommerce\WcGateway\WCGatewayModule->register_wc_tasks(Object(WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Container\ReadOnlyContainer)) #6 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php(530): WooCommerce\PayPalCommerce\WcGateway\WCGatewayModule->run(Object(WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Container\ReadOnlyContainer)) #7 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php(405): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package->doExecute() #8 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php(40): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package->boot() #9 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(77): {closure}('/home/customer/...') #10 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(92): WooCommerce\PayPalCommerce\init() #11 /home/customer/www/staging2.westfallsupply.com/public_html/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCommerce\{closure}('') #12 /home/customer/www/staging2.westfallsupply.com/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(Object(Woo_Mailerlite), Array) #13 /home/customer/www/staging2.westfallsupply.com/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #14 /home/customer/www/staging2.westfallsupply.com/public_html/wp-settings.php(555): do_action('plugins_loaded') #15 /home/customer/www/staging2.westfallsupply.com/public_html/wp-config.php(106): require_once('/home/customer/...') #16 /home/customer/www/staging2.westfallsupply.com/public_html/wp-load.php(50): require_once('/home/customer/...') #17 /home/customer/www/staging2.westfallsupply.com/public_html/wp-login.php(12): require('/home/customer/...') #18 {main} Next Exception: Can't obtain the container instance at this point of application. in /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php:701 Stack trace: #0 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php(639): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package->assertStatus(4, 'obtain the cont...', '>=') #1 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php(42): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package->container() #2 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(77): {closure}('/home/customer/...') #3 /home/customer/www/staging2.westfallsupply.com/public_html/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(92): WooCommerce\PayPalCommerce\init() #4 /home/customer/www/staging2.westfallsupply.com/public_html/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCommerce\{closure}('') #5 /home/customer/www/staging2.westfallsupply.com/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(Object(Woo_Mailerlite), Array) #6 /home/customer/www/staging2.westfallsupply.com/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #7 /home/customer/www/staging2.westfallsupply.com/public_html/wp-settings.php(555): do_action('plugins_loaded') #8 /home/customer/www/staging2.westfallsupply.com/public_html/wp-config.php(106): require_once('/home/customer/...') #9 /home/customer/www/staging2.westfallsupply.com/public_html/wp-load.php(50): require_once('/home/customer/...') #10 /home/customer/www/staging2.westfallsupply.com/public_html/wp-login.php(12): require('/home/customer/...') #11 {main} thrown

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

    (@virtualgeo)

    I too, after updating from version 2.9.0 to 2.9.1, encountered a fatal error on my test server.

    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 /var/www/html/wp_ic_eu/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php on line 37 and defined in /var/www/html/wp_ic_eu/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php:244 Stack trace: #0 /var/www/html/wp_ic_eu/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php(37): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package->addModule() #1 /var/www/html/wp_ic_eu/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(77): {closure}() #2 /var/www/html/wp_ic_eu/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(92): WooCommerce\PayPalCommerce\init() #3 /var/www/html/wp_ic_eu/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCo in /var/www/html/wp_ic_eu/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php on line 244

    Thread Starter lukeatsayhellotowoo

    (@lukeatsayhellotowoo)

    Are you running plugin code snippets? I found one of the php functions causing the error.

    gferguson78

    (@gferguson78)

    I was having the same issue and it seems that disabling this code snippet resolved the error :

    add_filter( 'woocommerce.feature-flags.woocommerce_paypal_payments.paylater_configurator_enabled', '__return_false' );

    I don’t know if that’s the only issue but I’d wait on an official fix before updating on a live site.

    Thread Starter lukeatsayhellotowoo

    (@lukeatsayhellotowoo)

    I had the same exact code. Removing that function worked for me as well. Good luck out there.

    thilo72

    (@thilo72)

    I have the same issue today after automatic update to 2.9.1 but have no such snippet or any other snippet related to this plugin. After disabling the woocommerce paypal payments plugin the site works fine again. But it is a problem for me, since this is my main payment option for customers.

    Here is the message I received for fatal error: Ein Fehler vom Typ E_ERROR wurde in der Zeile 244 der Datei /var/www/vhosts/fleurdekoer.de/httpdocs/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php verursacht. Fehlermeldung: 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/fleurdekoer.de/httpdocs/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php on line 37 and defined in /var/www/vhosts/fleurdekoer.de/httpdocs/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php:244

    Thread Starter lukeatsayhellotowoo

    (@lukeatsayhellotowoo)

    Are we all using Shoptimizer Theme? I would check if you have anything cutomized with the PayLater feature.

    thilo72

    (@thilo72)

    No, I have no customization for PayLater and I am running one website on Shoptimizer and another on Storefront Theme with similar plugins and I have the same issue on both websites with the woocommerce paypal payments plugin. Disabling it solved the problem on both websites. For me, this looks very strongly like an imcompatibility of this very plugin with a certain setup of a wordpress site but we still don’t know which similarity we all share that causes the conflict.

    Plugin Support Krystian

    (@inpsydekrystian)

    Hello @lukeatsayhellotowoo

    Thank you for reaching out. The error you’re encountering is caused by the use of a snippet responsible for disabling the Pay Later configurator. I’ve already forwarded this information to our developers for further investigation.

    We’ll keep you updated as soon as we have a solution.

    Hello @thilo72

    Disabling it solved the problem on both websites. For me, this looks very strongly like an imcompatibility of this very plugin with a certain setup of a wordpress site but we still don’t know which similarity we all share that causes the conflict.

    The issue you’re reporting is different from the one @lukeatsayhellotowoo encountered, which is why we always recommend opening your own thread. In your case, the error is unrelated, and the problem has been described in more detail here: link. Its caused by YITH plugin.

    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.

    Kind regards,
    Krystian

    thilo72

    (@thilo72)

    @inpsydekrystian Thanks for the feedback. Since there is another thread already I won’t start a new one. Just to mention on the other website I mentioned I have also a problem with the latest update and no PayLater snippet and no YITH. Don’t you think that your changes in the plugin would have justified to call it a 3.0 rather than a 2.9.1 indicating there are only minor changes with no relevant conflict potential? Many people have set up rules for automatic updating based on the minor vs major updates. Just a thought. I’m out here now. PS: However, your quick response and free support is highly appreciated!

    Plugin Support Krystian

    (@inpsydekrystian)

    Hello @thilo72

    Thank you for your feedback, and I appreciate your thoughts.

    We always suggest users create their own dedicated threads because, otherwise, it often leads to confusion within the thread. We do this to keep things organized and ensure every issue gets the proper attention.

    If you’re encountering a fatal error of any kind, please create a new thread with the logs of the fatal error and the system report, and we’ll do our best to help you sort it out.

    As for your point on version numbers, we agree that larger updates may warrant a more significant version change. We are reserving 3.0 for an upcoming bigger update, so stay tuned for that.

    Kind Regards,
    Krystian

    Plugin Support Krystian

    (@inpsydekrystian)

    Hello @lukeatsayhellotowoo

    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

    Update the ytih plugins first before update paypal, if can′t go to wp-content/plugins/ folder and rename paypal plugin, then back to wordpress and update yith plugins. Now revert the paypal plugin folder to the original name

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