Critical Error while update to 2.0.

  • Resolved shanrocks666

    (@shanrocks666)


    1 year, 11 months ago

    Hi,

    Is this error a known bug

    An error of type E_ERROR was caused in line 105 of the file
../plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Settings/SettingsRenderer.php.
Error message: Uncaught TypeError: Argument 1 passed to
WooCommerce\PayPalCommerce\WcGateway\Settings\SettingsRenderer::__construct()
must be an instance of
WooCommerce\PayPalCommerce\Vendor\Psr\Container\ContainerInterface,
instance of WooCommerce\PayPalCommerce\WcGateway\Settings\Settings
given, called in
../plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/services.php
on line 272 and defined in
../plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Settings/SettingsRenderer.php:105
Stack trace:
#0 ../plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/services.php(272):
WooCommerce\PayPalCommerce\WcGateway\Settings\SettingsRenderer->__construct()
#1 ../plugins/woocommerce-paypal-payments/vendor/dhii/containers/src/DelegatingContainer.php(117):
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @shanrocks666,

    So far, we have seen one other report about this error after the 2.0 update, but while fixing it should not be a problem, it’s not yet clear how to reproduce it.
    Type errors like this are most often caused by a potential conflict with a different plugin. So you may want to perform 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 and if you find out which other plugin is causing the error.
    Thanks!

    Kind regards,
    Niklas

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @shanrocks666,

    We have not heard back from you in a while, so I’m marking this thread as resolved. Hopefully, the above information helped you out. We’ll be here to assist when you are ready to continue looking into this with us and want to reopen this thread or create a new one.

    We are still interested to know if this problem persists for you with the latest update 2.0.1, as the update improves the compatibility with certain third-party plugins.
    Thanks!

    Kind regards,
    Niklas

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Critical Error while update to 2.0.’ is closed to new replies.