I uncovered this when testing https://drupal.org/comment/8397545#comment-8397545

Running htmltidy 7.x-1.x-dev and "HTML Tidy for Mac OS X released on 25 March 2009" (gee that's old)

* when submitting really bad content, it exits (error level 2) instead of (warning level 1) and returns the *untouched* bad source. But quietly.
It looks like - with the above tidy binary, the module currently expects WARNINGS to be returned on STDERR but ERRORS to be returned on STDOUT.
Today I am seeing the ERROR come out on STDERR (makes sense) but the module is not using it from there.

As this used to be correct once upon a time, I suspect that this may be a behavior change in the binary or build.

Comments

dman’s picture

dman CreditAttribution: dman commented

I have some patch fixes that now catch this, though it also involves something of a repair to the other verbose debug reporting that was scattered through the system. looks like the logging system never really made it through to the D7 port, and nobody ever noticed, so I'm just dropping that drupal-5 era sort of stuff.
I have solutions in code ready, just pending other checks on my end.