Skip to main content
Miguel-F
Miguel-F
Inspiring
November 8, 2010
Answered

Can you specify a missing template handler that lives under another site?

  • November 8, 2010
  • 1 reply
  • 3833 views

I have configured a dedicated site, separate from my website, for my ColdFusion administrator (CFIDE).  So I have my website here: http://www.public-site.com/ and my ColdFusion admin here: http://www.cfadmin-site.com/ .  They both live on the same server but under different directories.  So now I am configuring my ColdFusion settings and wondering if there is some way to configure the missing template handler and site-wide error handler to use files that live under the public site directory so that I can give my users a consistent look?

I am guessing that this is not possible but thought I would ask.  I may be left with creating the modules under my ColdFusion admin directory and then using <cflocation> to redirect the user back to the public website environment.  Or embedding some javascript to redirect them.  Any other thoughts?

    This topic has been closed for replies.
    Correct answer ilssac

    I have ColdFusion installed as J2EE and am using the builtin JRun application server.  I am only running one instance of ColdFusion.  I have also disabled the JRun webserver so nothing is browsable from the cfusion-war directory.  (Although I think the JRun/IIS connector still looks in that directory.)  So my ColdFusion webroot is the same as my IIS webroot for the cfadmin site.

    Mine looks like this:

    IIS web roots

         D:\wwwroot\public-site\

         D:\wwwroot\cfadmin-site\

    ColdFusion web root

         D:\wwwroot\cfadmin-site\

    Of course, the ColdFusion administrator is looking for the handler files in that cfadmin-site directory (as you have yours setup).  There is probably no way around this and that's okay I guess.  Do you see any issue with me setting up my handler to redirect back to the public site after it processes?


    Miguel_ wrote:


    ColdFusion web root

         D:\wwwroot\cfadmin-site\

    If that is your ColdFusion webserver, then YES that is where you put the site wide handlers.

    I'm not sure about your statement that you need to "redirect back to the public site".  As Far As I Know, ColdFusion should see any sitewide content from that directory from the context of the IIS website that is processing a request for.

    It would take some testing (and if you have already then ok) but my first thought would we No you don't need to redirct because you are already there.

    1 reply

    ilssac
    ilssac
    Inspiring
    November 8, 2010

    What flavor of ColdFusion are you using (standard, stand-alone, multi-instance, J2EE).

    The sitewide missing template handler, is based on the ColdFusion web root, which can be different then the web server web root, which you listed in your original post.

    Miguel-F
    Miguel-FAuthor
    Inspiring
    November 8, 2010

    Sorry, should have posted that.  I'm using ColdFusion 9.0.1 Enterprise and Windows Server 2008 (IIS 7).

    Yes, these settings are relative to the ColdFusion web root and mine is now different.  Like I said, I don't think this is possible but thought I would ask. 

    ilssac
    ilssac
    Inspiring
    November 8, 2010

    Miguel_ wrote:

    Sorry, should have posted that.  I'm using ColdFusion 9.0.1 Enterprise and Windows Server 2008 (IIS 7).

    Yes, these settings are relative to the ColdFusion web root and mine is now different.  Like I said, I don't think this is possible but thought I would ask. 

    ColdFusion Enterprise only eliminates Standard.  Did you configure the Enterprise as Standard, Multiple Instance or J2EE.

    You have NOT listed the ColdFusion web roots (most likely).  You have listed the Web Server (IIS) web roots.  Yes you have two of those, but do you have one or two ColdFusion web roots?  Depends on how you have configured your ColdFusion Application Server.

    For Example, On one of my servers, I have a dozen web sites, including one Dedicated to ColdFusion Just like you have done.  I also have three ColdFusion instances configured using the Multiple Instance version of ColdFusion.  So I have 12 IIS web roots and three ColdFusion web roots.  The Site Wide Missing Template Handler and Site Wide Exception Handler go into the ColdFusion web Roots.

    I.E.

    IIS Web Roots

    • D:\IntranetSites\Registration\
    • D:\IntranetSites\Information-Technology\
    • D:\IntranetSites\ets-internal\
    • D:\IntranetSites\enforcement\
    • D:\IntranetSites\administration\
    • E:\WebServerAdmin\
    • ETC

    ColdFusion Web Roots

    • E:\jrun4\servers\cfusion\cfusion-ear\cfusion-war
    • E:\jrun4\servers\general\cfusion.ear\cfusion.war
    • E:\jrun4\servers\general2\cfusion.ear\cfusion.war

    It is the latter three where I put my Site Wide handler files.  And then the file in each JRun server would apply to all the web sites connected to that ColdFusion server instance with the web server connector.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices