Problem with cfoutput

Dinghus wrote:
> It isn't the error page itself that is the problem, nor is it the error. Take a look at the output for the DATE and TIME. I am actually getting the line of code vice the output.

Is that an <cferror> page? It looks like it because of #error#
structure. As such a page there or specific limitations to what can be
done on such a page as described in the documentation. Note in the
following documentation that validation and request errors can not use
any CFML. That means those dateFormat() and timeFormat() functions are
going to be ignored by such a page.

http://livedocs.adobe.com/coldfusion/8/htmldocs/Errors_09.html
Creating an error application page

The following table lists the rules and considerations that apply to
error application pages:

Type


Considerations

Validation
* Cannot use CFML tags.
* Can use HTML tags.
* Can use the Error.InvalidFields, Error.validationHeader, and
Error.validationFooter variables by enclosing them with number signs (#).
* Cannot use any other CFML variables.

Request
* Cannot use CFML tags.
* Can use HTML tags.
* Can use nine CFML error variables, such as Error.Diagnostics, by
enclosing them with number signs.
* Cannot use other CFML variables.

Exception
* Can use full CFML syntax, including tags, functions, and variables.
* Can use nine standard CFML Error variables and cfcatch variables.
Use either Error or cferror as the prefix for both types of variables.
* Can use other application-defined CFML variables.
* To display any CFML variable, use the cfoutput tag.

It isn't the error page itself that is the problem, nor is it the error. Take a look at the output for the DATE and TIME. I am actually getting the line of code vice the output.

Seeing this,
Element MOO is undefined in ARGUMENT

the first thing I'd do is
<cfdump var="#arguments#">

Dinghus wrote:
>
> So why doesn't it work suddenly for 1 line?

Your error template is not failing. It is capturing an error from
somewhere else in the application. In other words, it is doing its job!

When one reads the error message one finds these four lines.
> You were trying to process /dtr/index.cfm?
> Message:
> Element MOO is undefined in ARGUMENT.
> The error occurred on line 11.

That says in the index.cfm page file on line 11 something is trying to
reference element 'MOO' in the structure 'ARGUMENT' and that structure
does not have such an element.

I'll bet dollars to doughnuts that some developer meant to type
*arguments*.moo.

HTH
Ian