Tres Seaver wrote:
richard@bizarsoftware.com.au wrote:
richard@bizarsoftware.com.au wrote:
The dtml-in batching mechanisms are quite difficult to debug - the DTML documentation I have has examples which break it and there's no indication of why. It turns out the DT_In renderwb() code gobbles all exceptions from the rendering of the previous and next blocks. I've hacked my code so that there's no try/except clause any more. I'm not sure what exception it's trying to catch, but could it perhaps be made a little more picky?
And here's a diff - I'm pretty sure this was the intended behaviour...
Please post this as a "Bug w/ patch" to the Collector:
http://classic.zope.org:8080/Collector
That way we don't lose your fix in the list traffic (losing it along with our marbles is another problem :)
Someone else responded to the list saying that he'd already done it. There was no match to my search of dtml-in though, so I've submitted a new bug report. Richard -- Richard Jones richard@bizarsoftware.com.au Senior Software Developer, Bizar Software (www.bizarsoftware.com.au)