Scott Laird <scott <at> sigkill.org> writes: > Check the logs; when an exception occurs in a filter, Typo stops > rendering the filtered text and sticks with the original source.
Yes, see my other message. I'm waiting for my hosting company to confirm whether it's a Ruby/OpenSSL issue. Logging of the macro execution _is_ pretty terse, and in production mode the error (because it _is_ an error) isn't even logged. > We > should probably clean this up a bit for macro filters; they should > fail on a line-by-line basis, but it looks like we're getting more of > an all-or-nothing failure pattern. Thanks, Steven. _______________________________________________ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list
