Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Message in stderr is breaking django-mjml

See original GitHub issue

The fix to issue #1342 released in version 4.2.1 is breaking django-mjml template engine. If using mjml v3 the message MJML v3 syntax detected, migrating to MJML v4 syntax. Use mjml -m to get the migrated MJML. is shown in stderr now, making django-mjml fail to render the template because it considers that any output in stderr an error running the command. With mjml v4.2.0 it works just fine.

Issue Analytics

State:
Created 5 years ago
Comments:10 (6 by maintainers)

Top GitHub Comments

1reaction

a14dcommented, Aug 25, 2021

I had this problem recently, the solution was to remove mj-container as mentioned here #1342 by @iRyusa

1reaction

tkafkacommented, Mar 6, 2019

Hi @ngarnier, I disagree with this - stdout should only be used for the actual output (so that you can redirect it to a file, and be sure you aren’t sending your users an email with validation messages).

All diagnostic output should go to stderr, and I propose to add setting to select verbosity (warnings and errors, or errors only).