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.
Currently Lingotek defines 2 types of messages in watchdog: "lingotek - api" and "lingotek - error".
The convention in Drupal core is to use one watchdog type for the owner of the message and the 'severity' property to describe the severity of the error. It would be helpful to be able to filter Lingotek messages according to this convention.
Comment | File | Size | Author |
---|---|---|---|
#1 | Recent_log_messages___Commons_7.x-3.4-RC1.png | 13.7 KB | ezra-g |
Comments
Comment #1
ezra-g CreditAttribution: ezra-g commentedComment #2
robertdbailey CreditAttribution: robertdbailey commentedThanks for the suggestion, we'll continue to whip this module into shape. I modified logging for the Lingotek module to use only module name in the message type and to use standardized severities. So, logging will now have just "Lingotek". This fix is currently in 7.x-4.x and will be going out in the release later this afternoon (7.x-4.05).
Comment #3
robertdbailey CreditAttribution: robertdbailey commentedAs a further followup on logging changes, we updated the location of overridden tags to be in the message title, rather than the beginning of the message's body. This was commit 50450a1b33f6e01e7f83fb02cd9a2af0911fb09b, and this is in dev (7.x-4.x) and will be released as part of 7.x-4.06.