Basically, what you are doing inside the loop is unnecessary, you already
have a cfoutput on the page.
Correction, the original author of the tag did that, not me.
I have it on my agenda to clean all those out, I was more making
reference to the fact that the bug didn't get caught in CFMX 7
Had an interesting issue come up on Friday - I had sent some code to a
client for a small job I was working on and got a message back that
there was a syntax error. I replied that it had not happened on my
setup and showed them via a series of screen shots; they replied with
a screen shot of the
Yup, it was something that cropped up back when CF6 came out. Putting code
from 6 to 5 highlighted this.
Ade
-Original Message-
From: C. Hatton Humphrey [mailto:[EMAIL PROTECTED]
Sent: 13 November 2005 19:12
To: CF-Talk
Subject: Error found by CF45 but Not CFMX7?
Had an interesting
You could say its no longer an error. I ran into this back when MX
came out. I was developing on a 6.0 dev box and porting live to a
4.5.1 box.
Not something you want to build into your code from scratch, but in a
pinch this loosening of the reins can be very handy. I am now porting
a CF5 app
Hatton,
Basically, what you are doing inside the loop is unnecessary, you already
have a cfoutput on the page.
In previous version of CF the only time you were allowed to nest cfoutputs
was inside a grouped query output. Now they've basically removed the check
from CFMX and beyond so that it is
5 matches
Mail list logo
