• Resolved graphiclux

    (@graphiclux)


    Installed the new plugin version and this broke the wp-admin of the website, giving this error.

    PHP message: PHP Fatal error: Declaration of Monolog\Logger::emergency(Stringable|string $message, array $context = []): void must be compatible with Psr\Log\LoggerInterface::emergency($message, array $context = []) in plugins/nitropack/nitropack-sdk/vendor/monolog/monolog/src/Monolog/Logger.php on line 683″ while reading response header from upstream

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support phristanov

    (@phristanov)

    Hey @graphiclux ,

    Thanks for taking the time to report this.

    We are already aware of the issue and our team is working on a fix.

    Best,
    Plamen, Head of Support at NitroPack

    Plugin Support phristanov

    (@phristanov)

    Hey @graphiclux ,

    I am happy to let you know that the issue has been fixed in our latest 1.17.8 version of the plugin.

    Best,
    Plamen, Head of Support at NitroPack

    Hello,

    i’ve had similar issue where i was unable to login. After the update to latest version, it still shows a critical error after login but after refreshing the page, it goes away. The logs show a different error related to Monolog. Our theme uses Rareloop’s Lumberjack framework which has Monolog in its dependencies. I already updated the composer dependencies and Monolog was updates to v2.10.0, but still get the same error after login:

    PHP Fatal error: Uncaught Error: Undefined constant Monolog\Utils::DEFAULT_JSON_FLAGS in /nas/content/live/sundance19/wp-content/themes/sundance-mtn-resort/vendor/monolog/monolog/src/Monolog/Formatter/NormalizerFormatter.php:35#012Stack trace:#012#0 /nas/content/live/sundance19/wp-content/themes/sundance-mtn-resort/vendor/rareloop/lumberjack-core/src/Application.php(171): Rareloop\Lumberjack\Providers\LogServiceProvider->register()#012#1 /nas/content/live/sundance19/wp-content/themes/sund..........

    Plugin Support phristanov

    (@phristanov)

    Hey @tiagogwm ,

    Thanks for reporting this.

    The issue should be fixed with 1.17.8 version of the plugin. However, we will be able to take a look but would you be so kind to contact us at [email protected] because we might need some additional information?

    Thanks in advance!

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