# [SOLVED] Acorn v3 -> v4 Upgrade | PSR Logger Issue -> Bedrock/WPML | Fatal error: Declaration of Monolog\Logger::emergency **URL:** https://discourse.roots.io/t/solved-acorn-v3-v4-upgrade-psr-logger-issue-bedrock-wpml-fatal-error-declaration-of-monolog-logger-emergency/26987 **Category:** acorn **Created:** 2024-04-15T09:16:57Z **Posts:** 13 ## Post 1 by @yasser_artcore — 2024-04-15T09:16:57Z **Edit** - This issue has been solved, the title has been updated to make this post easier to find for others. - **Looking for a solution?** - @alexmzk Provided a workaround below - @RistoKaalma pinpointed the issue in the WPML plugin and was marked as the solution for this thread * * * **Original Post** As recommended by Log1x on my [GitHub issue](https://github.com/roots/acorn/issues/372), I will try discourse to find a solution. **Summary** I have a project that’s kept up to dat using the latest bedrock, and sage theme. When I try to update acorn to v4.x _only when my application is set to the development environment_ I am getting a fatal error caused by Monolog, a dependency to Illuminate Log. **Steps that got me to the error** - Update the composer.json file to: `"roots/acorn": "^4.0"` - Run `composer update "roots/acorn" -W` **The Error** ``` 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 /Users/yasser/Artcore/artcore_bedrock_sofico_website/vendor/monolog/monolog/src/Monolog/Logger.php on line 681 ``` **Stacktrace** ``` Fatal error: Uncaught Error: Class "Monolog\Logger" not found in /Users/yasser/project/my_project/vendor/monolog/monolog/src/Monolog/Handler/AbstractHandler.php:60 Stack trace: - 0 /Users/yasser/project/my_project/vendor/monolog/monolog/src/Monolog/Handler/AbstractHandler.php(38): Monolog\Handler\AbstractHandler->setLevel(Object(Monolog\Level)) - 1 /Users/yasser/project/my_project/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php(49): Monolog\Handler\AbstractHandler->__construct(Object(Monolog\Level), true) - 2 /Users/yasser/project/my_project/vendor/illuminate/log/LogManager.php(189): Monolog\Handler\StreamHandler->__construct('/Users/yasser/M...', Object(Monolog\Level)) - 3 /Users/yasser/project/my_project/vendor/illuminate/log/LogManager.php(141): Illuminate\Log\LogManager->createEmergencyLogger() - 4 /Users/yasser/project/my_project/vendor/illuminate/log/LogManager.php(124): Illuminate\Log\LogManager->get('stack') - 5 /Users/yasser/project/my_project/vendor/illuminate/log/LogManager.php(681): Illuminate\Log\LogManager->driver() - 6 /Users/yasser/project/my_project/vendor/roots/acorn/src/Illuminate/Foundation/Exceptions/Handler.php(317): Illuminate\Log\LogManager->error('Declaration of ...', Array) - 7 /Users/yasser/project/my_project/vendor/roots/acorn/src/Illuminate/Foundation/Exceptions/Handler.php(278): Illuminate\Foundation\Exceptions\Handler->reportThrowable(Object(Symfony\Component\ErrorHandler\Error\FatalError)) - 8 /Users/yasser/project/my_project/vendor/roots/acorn/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php(183): Illuminate\Foundation\Exceptions\Handler->report(Object(Symfony\Component\ErrorHandler\Error\FatalError)) - 9 /Users/yasser/project/my_project/vendor/roots/acorn/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php(231): Illuminate\Foundation\Bootstrap\HandleExceptions->handleException(Object(Symfony\Component\ErrorHandler\Error\FatalError)) - 10 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->handleShutdown() - 11 {main} thrown in /Users/yasser/project/my_project/vendor/monolog/monolog/src/Monolog/Handler/AbstractHandler.php on line 60 ``` Anyone has any ideas on how to resolve this? Thanks in advance! - Y --- ## Post 2 by @pcatapan — 2024-04-15T11:22:37Z > [@yasser_artcore](#): > > `Fatal error: Declaration of Monolog\Logger::emergency` Hi, I had the same problem, in my case the error was that a plugin loaded its PSR Log package as global and replaced the one loaded via composer I was able to identify the problem by entering `var_dump(class_exists('Psr\Log\LoggerInterface'), (new \ReflectionClass('Psr\Log\LoggerInterface'))->getFileName());` In my **bedrock-autoloader.php** , this way I realized that the project was loading the package from a different folder than the vendor’s. I hope this helps you. --- ## Post 3 by @yasser_artcore — 2024-04-15T12:20:09Z Thank you pcatapan for your answer! Unfortunately, the class does ‘not exist’, yet it loads it. Here’s the output from that `var_dump()` ``` bool(false) string(91) "/Users/yasser/project/my_project/vendor/psr/log/src/LoggerInterface.php" ``` - The interface does exist within my vendor folder - The weird fact is that everything runs fine when I run the project setup with the `production` environment. - When I just add `var_dump(class_exists('Psr\Log\LoggerInterface')); ` before the Autoloader in `bedrock-autoloader.php` is instantiated. I get a dump saying `bool(false)` but no more error… As I understand now, and from various searches. This could have something to do with a php-psr extension. But I have no psr extensions installed. I’ve found several people and threads about this issue. most blaming psr extensions. Though I have none installed. Some urls for context - [GitHub | Monolog - Class Monolog\Logger not found (my 2nd error)](https://github.com/Seldaek/monolog/issues/1876) - [GitHub | Monolog - Declaration of \* must be compatible - Blames Psr loaded as a dependency for something else, how could I debug this?](https://github.com/Seldaek/monolog/issues/1808) - [GitHub | Monolog - similar to previous issue, yet proven that it’s not the ext-psr as suggested in most threads](https://github.com/Seldaek/monolog/issues/1764) So I really feel like it has something to do with a wrong Psr version? yet I am not requiring any PSR in my composer.json --- ## Post 4 by @alexmzk — 2024-04-15T16:03:18Z @yasser_artcore I have the same problem as you, but in my case, the WooCommerce Germanized Plugin is causing the issue by including an old version of PSR. So far, I don’t have a solution for this other than deactivating the plugin in development and only activating it in staging and production. :confused: **EDIT** I ended up disabling error reporting for the plugin folder in the development environment with a mu-plugin: ```

%s

', esc_attr($class), esc_html($message)); } ``` --- ## Post 5 by @RistoKaalma — 2024-04-16T07:13:29Z @yasser_artcore are you using: 1. Bedrock 2. WPML In general, if you are using WPML plugin, try commenting out the following part (~ line 65): ``` # wpml-multilingual-cms/vendor/composer/autoload_static.php 'Psr\\Log\\' => array ( 0 => __DIR__. '/..' . '/psr/log/Psr/Log', ), ``` Does it change anything? --- ## Post 6 by @yasser_artcore — 2024-04-16T07:33:48Z @alexmzk , Thanks for your reply! You helped a lot, thank you for the example. It does prove that it’s probably plugin related code . Love the solution you found! * * * @RistoKaalma Amazing! You nailed it :smiley: It is indeed WPML and your solution fixed it! Thanks a lot! * * * Unfortunately as this time, even the latest version of WPML has this issue. I’ll open a support thread with them --- ## Post 7 by @RistoKaalma — 2024-04-16T07:52:08Z Perhaps you don’t need to start a duplicate support thread on WPML - fellow [Roots.io](http://Roots.io) members are on it already: 1. [Fatal error: Declaration of Monolog - WPML](https://wpml.org/forums/topic/fatal-error-declaration-of-monolog/) 2. [https://github.com/mollie/WooCommerce/issues/892](https://github.com/mollie/WooCommerce/issues/892) When using Bedrock for managing plugins with composer, [composer-patches](https://github.com/cweagans/composer-patches) (shout-out to @tombro for the suggestion) might be useful until WPML v4.7 is released. In Bedrock dir: 1. Run `composer require cweagans/composer-patches` 2. Add to `"config"` → `"allow-plugins"` in in composer.json: ``` [...], "cweagans/composer-patches": true ``` 1. Add to `"extra"` in composer.json: ``` [...], "patches": { "wpml/wpml-multilingual-cms": { "Fix monolog": "patches/wpml-multilingual-cms/monolog-fix.patch" } } ``` 1. Write to `patches/wpml-multilingual-cms/monolog-fix.patch` file: ``` --- a/vendor/composer/autoload_static.php +++ b/vendor/composer/autoload_static.php @@ -62,10 +62,10 @@ array ( 0 => __DIR__. '/..' . '/symfony/polyfill-ctype', ), - 'Psr\\Log\\' => - array ( - 0 => __DIR__. '/..' . '/psr/log/Psr/Log', - ), + // 'Psr\\Log\\' => + // array ( + // 0 => __DIR__. '/..' . '/psr/log/Psr/Log', + // ), 'PhpMyAdmin\\SqlParser\\' => array ( 0 => __DIR__. '/..' . '/wpml/sql-parser/src', ``` 1. Manually delete `web/app/plugins/wpml-multilingual-cms` dir For me, seemingly it only ran when a plugin is being initially installed (or maybe updated… ultimately the state needs to “change” for it to work) - thus I had to manually delete the existing plugin files. 1. Run `composer update` - my output: ``` xxx@yyy:~/Projects/example-web/site$ composer update Gathering patches for root package. Loading composer repositories with package information Updating dependencies Nothing to modify in lock file Installing dependencies from lock file (including require-dev) Package operations: 1 install, 0 updates, 0 removals Gathering patches for root package. Gathering patches for dependencies. This might take a minute. - Installing wpml/wpml-multilingual-cms (4.6.9): Extracting archive - Applying patches for wpml/wpml-multilingual-cms patches/wpml-multilingual-cms/monolog-fix.patch (Fix monolog) Generating optimized autoload files > Roots\Acorn\ComposerScripts::postAutoloadDump 68 packages you are using are looking for funding. Use the `composer fund` command to find out more! No security vulnerability advisories found ``` --- ## Post 8 by @oxyc — 2024-04-18T14:54:48Z Another incompatible plugin [Logger interface incompatible with Psr\Log\LoggerTrait:log() (968) · Issue #1518 · woocommerce/woocommerce-paypal-payments · GitHub](https://github.com/woocommerce/woocommerce-paypal-payments/issues/1518) --- ## Post 9 by @uxuitokyo — 2025-01-10T01:28:44Z Thanks for your detailed explanation! Still no sign of 4.7 I am failing at this step. Can’t see any patches folder anywhere. Any idea where it could be? > [@RistoKaalma](#): > > Write to `patches/wpml-multilingual-cms/monolog-fix.patch` --- ## Post 10 by @RistoKaalma — 2025-01-10T23:14:58Z You have the create the directory yourself as it’s not included in the initial Bedrock project - create the new file (relative to your Bedrock directory, where the `composer.json` is) to `./patches/wpml-multilingual-cms/monolog-fix.patch`. Then copy all the content from code block (step 4) into the created `monolog-fix.patch` file: > [@RistoKaalma](#): > > ``` > --- a/vendor/composer/autoload_static.php > +++ b/vendor/composer/autoload_static.php > @@ -62,10 +62,10 @@ > array ( > 0 => __DIR__. '/..' . '/symfony/polyfill-ctype', > ), > - 'Psr\\Log\\' => > - array ( > - 0 => __DIR__. '/..' . '/psr/log/Psr/Log', > - ), > + // 'Psr\\Log\\' => > + // array ( > + // 0 => __DIR__. '/..' . '/psr/log/Psr/Log', > + // ), > 'PhpMyAdmin\\SqlParser\\' => > array ( > 0 => __DIR__. '/..' . '/wpml/sql-parser/src', > ``` --- ## Post 11 by @uxuitokyo — 2025-01-11T09:30:36Z Wonderful thank you so much. That did the trick using sitepress-multilingual-cms 4.6.15 I just changed the folder name. --- ## Post 12 by @tombro — 2025-02-11T09:33:13Z Issue has NOT been fixed in 4.7. The patch I created no longer works with 4.7. I updated the patch for 4.7. Haven’t tested thoroughly, but seems to work on this one site locally ``` --- www/app/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/lib/Php/Logger/DebugFileLogger.php 2025-02-05 11:41:18 +++ www/app/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/lib/Php/Logger/DebugFileLogger-fix.php 2025-02-11 10:27:03 @@ -5,7 +5,7 @@ class DebugFileLogger extends \Psr\Log\AbstractLogger { - public function log( $level, $message, array $context = array() ) { + public function log( $level, $message, array $context = array() ) : void { if ( ! defined( 'WP_DEBUG' ) || ! WP_DEBUG ) { return; } --- www/app/plugins/sitepress-multilingual-cms/vendor/composer/autoload_static.php 2024-03-29 16:31:17 +++ www/app/plugins/sitepress-multilingual-cms/vendor/composer/autoload_static-fix.php 2024-03-29 16:31:44 @@ -61,11 +61,11 @@ 'Symfony\\Polyfill\\Ctype\\' => array ( 0 => __DIR__. '/..' . '/symfony/polyfill-ctype', - ), - 'Psr\\Log\\' => - array ( - 0 => __DIR__. '/..' . '/psr/log/Psr/Log', ), + // 'Psr\\Log\\' => + // array ( + // 0 => __DIR__. '/..' . '/psr/log/Psr/Log', + // ), 'PhpMyAdmin\\SqlParser\\' => array ( 0 => __DIR__. '/..' . '/wpml/sql-parser/src', ``` see [Fatal error: Declaration of Monolog - WPML](https://wpml.org/forums/topic/fatal-error-declaration-of-monolog/#post-16690445) --- ## Post 13 by @tombro — 2025-02-28T11:31:17Z This has been fixed in 4.7.1. There is finally no more need for this patch.