> When I use <cfcontent type="whatever/ext"
file="somefile.ext"> in an action
> page called by a form, any code that follows cfcontent
in the action page does
> not execute. In other words, cfcontent is acting like
<cfabort>. the
> cfcontent tag is working exactly as expected, except it
halts the code.
>
> Is there anything I can do about this?
I wouldn't have expected this to be the case, but it's
certainly what I'm
seeing too.
I suppose the code monkeys at Allaire figured that CF's job
in the mix is
very "response-centric", and once the response has been
finalised, there's
no need to continue processing.
I beg to differ here. Obviously once one's done the
CFCONTENT, then that's
it as far as OUTPUT goes, but there should be no reason why
further
processing shouldn't be allowed, just like if the last line
which outputs
text in a "normal" CFML template might be on line 10, but
there might be 40
lines of code after that. There's nothing wrong with *that*,
is there? (He
asks, rhetorically).
I'd raise a bug / feature request if I was you.
--
Adam