• Resolved standerksen

    (@standerksen)


    I am getting the following error using PHP 8.2, WooCommerce 8.9.3 and Mollie Payments 7.5.5.

    Compile Error: Declaration of Psr\Log\NullLogger::log($level, $message, array $context = []) must be compatible with Psr\Log\AbstractLogger::log($level, Stringable|string $message, array $context = []): void

    What do I do to fix it?

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter standerksen

    (@standerksen)

    Problem persists after updating WooCommerce to 9.0.2.

    Plugin Support Femi

    (@femiyb)

    Hello @standerksen

    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 Mollie Payments for WooCommerce 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.

    Regards,
    Femi.

    Thread Starter standerksen

    (@standerksen)

    Unfortunately the issue still persists…

    Plugin Support Femi

    (@femiyb)

    Hello @standerksen

    Could you please confirm if this issue persists with the latest release, version 7.6.0?

    Regards,
    Femi.

    Hello,

    Sorry to highjack this thread, but we get a similar fatal error, using version 7.8.0.

    Our fatal error:
    Fatal error: Declaration of Mollie\WooCommerce\Log\WcPsrLoggerAdapter::log($level, $message, array $context = []) must be compatible with Psr\Log\AbstractLogger::log($level, Stringable|string $message, array $context = []): void

    We can ‘solve’ it by changing a line in the file mollie-payments-for-woocommerce > src > Log > WcPsrLoggerAdapter.php

    Line 75. From:
    public function log($level, $message, array $context = [])
    To:
    public function log($level, $message, array $context = []): void

    But this is not ideal, since we get a fatal error every time while updating and have to update this file again.

    We found this support ticket that seem to talk about the same issue:
    https://www.ads-software.com/support/topic/php-8-1-psr-3-0-0-compatibility/

    Hope you guys can have a look!

    Plugin Support Syde Joost

    (@joostvandevijver)

    Hello @standerksen

    since we did not hear back from you, we will mark this thread as resolved. Please let us know if you still require support on this issue.

    @gys1984 please open a new thread if you still need support. We you can follow a thread if it is the same, but if you need personal support on any matter, you should really open your own thread.

    Kind regards,
    Joost

    Thread Starter standerksen

    (@standerksen)

    Issue still persists in version 7.8.0…

    Thread Starter standerksen

    (@standerksen)

    As @gys1984 mentioned, there’s no conflict between themes or plugins. The only thing that solves the problem for me is going to public\content\plugins\mollie-payments-for-woocommerce\vendor\psr\log\Psr\Log\NullLogger.php and adding return type void to line 26 as such: public function log($level, $message, array $context = array()): void.

    Thread Starter standerksen

    (@standerksen)

    I have found additional information in the WooCommerce logs. Apparently the Mollie plugin is not compatible with the WooCommerce plugin itself, as a file in the plugin (class-woocommerce.php) throws the error.

    "backtrace": [
    {
    "file": "[...]\public\content\plugins\woocommerce\includes\class-woocommerce.php",
    "line": 405,
    "function": "critical",
    "class": "WC_Logger",
    "type": "->"
    },
    {
    "function": "log_errors",
    "class": "WooCommerce",
    "type": "->"
    }
    ]

    Hope this helps!

    Plugin Support Femi

    (@femiyb)

    Hello @standerksen

    Could you please confirm if this issue persists with the latest version of the Mollie for WooCommerce Payments plugin?

    Regards,
    Femi.

    Thread Starter standerksen

    (@standerksen)

    Version 7.8.2 seems to solve the issue, thank you very much!

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