DrupalConsoleLogger::log() fatals on PSR-3 Stringable messages [#3616478]

Problem/Motivation

DrupalConsoleLogger::log() passes $message to strtr() without casting it to string. PSR-3 allows Stringable messages. TranslatableMarkup is one. That causes:

TypeError: strtr(): Argument #1 ($string) must be of type string, Drupal\Core\StringTranslation\TranslatableMarkup

Steps to reproduce

\Drupal::logger('test')->warning(new TranslatableMarkup('Value %v is invalid.'), ['%v' => 'x']);

Proposed resolution

Cast $message to string before placeholder replacement.

Comment	File	Size	Author
	core-03-console-logger-stringable-message.patch	906 bytes	luigisa

Issue fork drupal-3616478

Show commands

Start within a Git clone of the project using the version control instructions.

Add & fetch this issue fork’s repository

Or, if you do not have SSH keys set up on git.drupalcode.org:

Add & fetch this issue fork’s repository

3616478-drupalconsoleloggerlog-fatals-on changes, plain diff MR !16704
Check out this branch for the first time

Check out existing branch, if you already have it locally

About issue forks

Comments

Comment #1

13 August 2026 at 11:39

luigisa created an issue. See original summary.

Comment #2

luigisa commented 13 August 2026 at 11:47

Issue summary:	View changes
Related issues:		+#3613129: TypeError: strtr(): Argument #1 ($string) must be of type string, Drupal\Core\StringTranslation\TranslatableMarkup given

Comment #3

smustgrave commented 13 August 2026 at 12:28

Status:	Needs review	» Needs work
Issue tags:		+Needs tests

Fixes need to be in MRs and as a bug test coverage

Comment #4

quietone commented 13 August 2026 at 12:34

Version:	11.x-dev	» main
Issue tags:		+Needs merge request

Hi, thanks for the issue and the patch! Issues for Drupal core should be targeted to the 'main' branch, our primary development branch. Changes are made on the main branch first, and are then back ported as needed according to the Core change policies. The version the problem was discovered on should be stated in the issue summary Problem/Motivation section. Thanks.

If AI was used in any way to created the issue or the fix The Drupal policy is that the use must be stated on the issue. Refer to the policy on the use of AI when contributing to Drupal includes that the use of AI must be disclosed.

The needs an MR to be ready for review.

Comment #5

quietone commented 13 August 2026 at 12:35

Title:	DrupalConsoleLogger::log() fatals on PSR-3 Stringable messages, taking down web requests since the logger.console service is tagged as a logger	» DrupalConsoleLogger::log() fatals on PSR-3 Stringable messages
Issue summary:	View changes

Updating the title per Title guidelines.