I actually found a better way around it. I noticed that we had some images that 
worked correctly on other pages. They were in their own table. So I just put 
these inside another table and put the <td> and </td> inside the <cfoutput> and 
</cfoutput>. It puts the space like this: </td> <td> but we all know _that_ 
space is ignored by the browser.

I'm still irritated, but the client will never know the difference. It really 
does defeat my reason for using cfsetting there.

Quoting Jann VanOver <[EMAIL PROTECTED]>:

> The problem is not the <cfoutput>, but the return AFTER the cfoutput. 
> I
> agree this is a flaky implementation when suppression is turned on.
> 
> To make it look better for the customer, try this - remove the returns
> after
> </cfoutput> and before the next <cfoutput> like this:
>  
>  <td><cfsetting enablecfoutputonly="Yes">
>   <cf_getsomeinfo id="2">
>   <cf_getsomeotherinfo id="#request.getsomeinfo.imageid#">
>   <cfoutput><img 
> src="#request.getsomeotherinfo.imagesrc#"></cfoutput><cf_getsomeinfo
> id="4">
>   <cf_getsomeotherinfo
> id="#request.getsomeinfo.imageid#"><cfoutput><img
> src="#request.getsomeotherinfo.imagesrc#"></cfoutput>
>  <cfsetting enablecfoutputonly="no"></td>
> 
> On 5/29/02 2:08 PM, "mr_urc" <[EMAIL PROTECTED]> wrote:
> 
> > I have this code (actual custom tags removed to protect the
> innocent):
> > 
> > <td><cfsetting enablecfoutputonly="Yes">
> >  <cf_getsomeinfo id="2">
> >  <cf_getsomeotherinfo id="#request.getsomeinfo.imageid#">
> >  <cfoutput><img
> src="#request.getsomeotherinfo.imagesrc#"></cfoutput>
> >  <cf_getsomeinfo id="4">
> >  <cf_getsomeotherinfo id="#request.getsomeinfo.imageid#">
> >  <cfoutput><img
> src="#request.getsomeotherinfo.imagesrc#"></cfoutput>
> > <cfsetting enablecfoutputonly="no"></td>
> > 
> > Now here's my problem. The output looks like this:
> > <td><img src="path/imagename1.gif"> <img src="path/imagename2.gif">
> </td>
> > 
> > Now this is really bad. I need to eliminate that extraneous space or
> the
> > images 
> > don't butt up against each other and the design is screwed. After
> much
> > thought, 
> > I did this:
> > <td><cfsetting enablecfoutputonly="Yes">
> >  <cf_getsomeinfo id="2">
> >  <cf_getsomeotherinfo id="#request.getsomeinfo.imageid#">
> >  <cfoutput><img
> src="#request.getsomeotherinfo.imagesrc#"><!--</cfoutput>
> >  <cf_getsomeinfo id="4">
> >  <cf_getsomeotherinfo id="#request.getsomeinfo.imageid#">
> >  <cfoutput>--><img
> src="#request.getsomeotherinfo.imagesrc#"><!--</cfoutput>
> > <cfsetting enablecfoutputonly="no">--></td>
> > 
> > This fixes the problem, because apparently, the extraneous space is
> being
> > outputed by the </cfoutput> tag. (It couldn't be outputted by one of
> our
> > custom 
> > tags because no custom tag is called between the last </cfoutput> and
> the
> > <cfsetting>.) 
> > 
> > Now it looks like:
> > <td><img src="path/imagename1.gif"><!-- --><img
> src="path/imagename2.gif"><!--
> > -
> > -></td>
> > 
> > But I'm irritated that I have to repeat the functionality of
> cfsetting
> > enablecfoutputonly="yes" after calling it. Besides, it totally messes
> up the
> > display in CF Studio.
> > 
> > I've searched the Macromedia website for some help, but didn't find
> anything
> > that applied. Does anybody know if there is a patch for this for
> version 5?
> > 
> > The client specifically asked that we change all <!-- and --> to <!---
> and
> > ---> 
> > and I really don't want to tell them that those are in there to work
> around a
> > bug.
> > --
> > If you hate the interface, blame Kevin.
> > 
> 
______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to