Keep application.cfm include from displaying

[EdmondsM]

Hi All, I have a application.cfm file that puts a header menu at the top of
every page. the problem that I am having is when I call a popup window the
header displays as well. Is there a way to prevent this from happening??

thanks in advance

maurice

[Stressed_Simon]

You shouldn't really have visual elements in your Application.cfm, but you can
achieve what you want.

Either, put the template for the pop-up in it's on folder with it's own
Application.cfm.

Or

Make the pop-up a .html file.

Or

Use this combination of functions to test if it the Pop-Up:-

<cfif GetFileFromPath(GetBaseTemplatePath()) IS NOT "myPopUp.cfm">
<cfinclude template="myNavigation.cfm">
</cfif>

[EdmondsM]

Hi Simon, where is the best place to put visual elements if you want them to display on everypage??

[Stressed_Simon]

I normally create a Dreamweaver Template, and use cfincludes in that. Then, if
I need to create pages that don't need these, then I don't have to muck about
with my logic to get it to work.

Does that make sense?

[EdmondsM]

ok, that makes alot of since. I have a templete already, so I can just add it to the top of every page instead of using the application.cfm to display it on every page.

[Stressed_Simon]

That's right. Really try and keep visual elements out of Application.cfm and OnRequestEnd.cfm, this also goes for the Appliction.cfc in CFMX7.

[EdmondsM]

Thanks Simon. I will make a mental note of that one. Since you mention application cfc.....is it true that in MX7 it is better to use application.cfc rather than application.cfm.

[Stressed_Simon]

It depends by what you mean by better? There is functionality that you can only
achieve with an Application.cfc, and if you are familiar with the use of
components then I would suggest it is the way to go. Also Application.cfm is
only supported in CFMX7 for backwards-compatibility reasons. However, in a
simple application you can get all you need from Application.cfm and
OnRequestEnd.cfm.

So in summary I would go the Application.cfc route if it is available to you
and you are comfortable with the execution, but be careful with the methods
that are executed outside of page requests as they are a swine to debug!!!!

[EdmondsM]

Thanks dude for your guidence. I will once again make a note of this.