You haven't done this before. This won't work on any version of CF as far as I know. Both the <cfifs> AND the <Cfoutputs> are broken into separate files. But don' t you think this is rather unwieldy? I'd hate to be troubleshooting code where a logic block starts in 1 file and ends someplace else. Perhaps you should rethink this. The purpose of includes is to make code reusable. So... presumably you would have several files with beginning CFIFS to handle this include right? I'm not sure that's a great approach.
Mark A. Kruger, CFG, MCSE www.cfwebtools.com www.necfug.com http://mkruger.cfwebtools.com -----Original Message----- <!--- content_block_1.cfm ---> <div class="margin_8 orange_link"> <cfoutput> <img src="#request.imagesdomain#spacer.gif" border="0" height="5" width="0"><br> <cfif isDefined('cookie.empower_login')> <!--- end content_block_1.cfm ---> <!--- content_block_2.cfm ---> <cfelse> To use this page, please first <a href="#request.commondomain#login_form.cfm">login</a>. </cfif> </cfoutput> </div> <!--- end content_block_2.cfm ---> This code works fine when not in the includes, but separated and made into includes, I get an error, "Context validation error for tag cfif" which refers to the <cfif isDefined('cookie.empower_login')>. I thought I'd broken up cfif statements into two pieces of an include before, but maybe not. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:206846 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
