Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Comment | File | Size | Author |
---|---|---|---|
#5 | Screenshot 2020-07-22 at 4.10.52 PM.png | 22.56 KB | msti |
#2 | level_100_is_not_defined-3157611-2.patch | 943 bytes | cosolom |
Issue fork monolog-3157611
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
cosolom CreditAttribution: cosolom commentedComment #3
lussolucaPls describe why we need this change
Comment #4
cosolom CreditAttribution: cosolom commentedWithout this change I got error "Level "100" is not defined, use one of: 100, 200, 250, 300..."
Comment #5
mstiI am also having this error, see attached screenshot.
My configuration: core 8.9.2, drupal/monolog 2.0.0-beta1 and monolog/monolog 2.1.0
The patched #2 fixes the error.
Comment #6
pdenooijer CreditAttribution: pdenooijer as a volunteer commentedRTBC +1
The problem is they are defined as strings in the services file, but they should be defined as integers instead. The setLevel method does this in
Monolog\Logger
:So it assumes it's a constant defined on the class instead of the log level we want. Please commit this for beta2.
Comment #8
lussolucaCommitted and pushed to 2.x, thanks!
I'm going to release a beta2.
Comment #10
mhmd CreditAttribution: mhmd as a volunteer and commentedThe issue still exist in beta 2, See #6.
Comment #11
pdenooijer CreditAttribution: pdenooijer as a volunteer commentedIt does not, for me beta2 works fine without a patch. So if you still see the problem your probably not on beta2.
Comment #12
SalvadorP CreditAttribution: SalvadorP as a volunteer commentedSeems that there is a different, possibly related error.
I'm seeing this:
Level "monolog.level.debug" is not defined, use one of: 100, 200, 250, 300, 400, 500, 550, 600
Checked the values on services.monolog.yml and they are integers, also checked the version in composer and I'm on beta 2.
Is a problem on my side?
Should I open a new bug, or it is related to the old one?
Comment #13
manojapare CreditAttribution: manojapare as a volunteer and commentedStill the error appears on beta2 version:
Will find out the reason why it is appearing, if valid can reopen this bug.
Comment #14
manojapare CreditAttribution: manojapare as a volunteer and commentedThis issue was reproducible only when using composer drupal/core and not while using drupal/core-recommended
So it should be related or because of some vendor library.
Comment #15
vladutstoicoiu CreditAttribution: vladutstoicoiu as a volunteer commentedI had also encounter this issue after I updated to drupal 9.x.
The problem was that inside the site specific services.yml (Eg: monolog.services.yml) the configuration
had "monolog.level.debug" instead of "%monolog.level.debug%".
Hope it helps.
Comment #16
bfuzze9898 CreditAttribution: bfuzze9898 as a volunteer commented#15 works... sort of.
It works AFTER monolog is installed, but it breaks on install/uninstall with the error:
If I switch it back to 'monolog.level.debug', then I can install/uninstall.
This is causing some issues with deployments. I think this issue should be reopened.
UPDATE: Just figured out that combining patch from #2 and #15 fixes both the notice and install/uninstall.
Comment #17
botanic_spark CreditAttribution: botanic_spark at FFW, Develomon commentedI am having the issue when installing the module if I have handler defined like this:
The error I am getting
You have requested a non-existent parameter "monolog.level.debug".