Failure with cfsetting and cfprocessingdirective?

Question

I have the following code buried deeply in our application.
I've tried to reproduce a simpler example without success. This
example clearly fails. What can I do to get the cfsetting and
cfprocessingdirective tags to work correctly?
The code:
<cfsavecontent
variable='AlsVar'><cfprocessingdirective
suppresswhitespace='yes'>before<CFSETTING
ENABLECFOUTPUTONLY="yes">
<cfloop index="i" from="1" to="6" step="1">
<cfif i mod 2>
#i# is Als odd<br>
<cfelse>
#i# is Als even<br>
</cfif>
</cfloop>
<CFSETTING
ENABLECFOUTPUTONLY="no">after</cfprocessingdirective>
</cfsavecontent>
<cfmail from="[email protected]"
to="[email protected]"
subject="ProcessTag:#strElementName#">#AlsVar#</cfmail>
The content of the email that I get is:
before
#i# is Als odd<br>
#i# is Als even<br>
#i# is Als odd<br>
#i# is Als even<br>
#i# is Als odd<br>
#i# is Als even<br>
after
Which shows that both tags are being ignored: There is output
outside the cfoutput tag AND the irregular spacing shows that
whitespace is not being suppressed.
As stated, when I try simpler examples, it works and the
documentation says that a "yes" in either tag overrides any number
of previous "no"s!

Answer 1

Adam,
Everything you are saying is exactly correct. That is why I
suspect the "tag library" answer is unfortunately the correct one.
Both the cfsetting and cfprocessing directive tags are defined such
that a "yes" overrides any number of previous "no"s! Thus, as far
as those directives are concerned, no outside state would (should)
impact them, by definition! In fact they are defined such that for
"ENABLECFOUTPUTONLY='yes'", the only thing that would permit output
is being contained inside "cfoutput" tags, (either inside or
outside the scope of the cfsetting tags, doesn't matter which).
Given the display of #i# instead of a number, no cfoutput tags are
operational, so no display should exist.
Thus the only thing that makes sense is PaulH's statement
that the tags are defined not to work inside tag libraries.
A] If they DO work inside a tag library (which I will test
when I get back to my office in a few days), then there is nothing
that is documented that states that the code I presented should not
work regardless of what is "surrounding" it! The bug is either
there or the external scope that overrides the tags isn't
documented!
B] If they DON'T work inside a tag library as PaulH states,
then I need to know how to reference a single piece of code from
almost 300 different domains without using a tag library!
(And, completely unrelated to this entire conversation, if
is true, then I personally believe that such behavior is a bug
that was documented as how it works instead of fixing it: I can't
see why putting code into a tag library and thus breaking it would
be considered "ok"-- but that's just me.)
If It does work in the tag library I will continue to try to
reproduce the problem so that it can be written up wither as a bug
or as documentation as to what undocumented external circumstances
prevent a simple cfloop from behaving properly inside the two
tags.