On Wed, 12 Jul 2000, Martijn Pieters wrote:
You are seeing transactions at work. Your DTML Method _is_ being processed, only an exception caused the publishing process to stop, roll back the transaction, and return the error message to you.
DTML is not a linear language like ASP, it is not processed one line at a time and bails out at the first error. DTML is parsed into an object tree when entered, and this tree it then later on asked to render itself. An exception in this tree will propagate down to the publishing level, and then turned into an error response. So DTML is, like Python and Java, object oriented and exception driven.
If you want to see how far a page gets, try using <dtml-try> blocks around parts of your code. You can then catch the exception higher in the object tree, and generate your own messages in reaction to this.
Fine... so my debuging techniques are less than perfect. I will change them in future. Thanks. That doesn't change my original problem, which everybody has so far decided to ignore. Curtis.