Actually, I didn't look at bug 548 before I did this this morning. :(
I instrumented one of the production webservers with cluck on that warning message, so this morning I could see exactly what path it took. After drilling down into that I found the problem with the HTML cleaner.
no subject
I instrumented one of the production webservers with cluck on that warning message, so this morning I could see exactly what path it took. After drilling down into that I found the problem with the HTML cleaner.
In any case, let me go comment on the bug.