I'm looking at the server in which the CF website is running off of and I can
get the CF pages to run and the CF to process properly but I cannot get the
graphics or css to display. I'm wondering if it has to do with the mappings.
The current mapping is:
Logical Path Directory Path
/CFIDE C:\Inetpub\wwwroot\CFIDE
/gateway C:\CFusionMX7\gateway\cfc
c_wigginton - 25 Jul 2007 22:01 GMT
The C:\CFusionMX7\wwwroot\AppName directory would work fine if you were using
the ColdFusion built-in webserver but it looks like an IIS installation, which
means that if your files are located in the C:\CFusionMX7\wwwroot\AppName, then
the IIS will need to have a virtual directory mapped to the ColdFusion wwwroot
\appname directory as part of the configuration, that or give you access to the
c:\inetpub\wwwroot directory or provide somesort of promotion mechanism to move
your app from development to production.
drdagwood - 26 Jul 2007 12:08 GMT
Although I'm not an IIS guru it seems to make sense about the IIS.
Three quick questions then :
(1) How come the pages still display and not the graphics, css or swf files?
(2) How come CF still works if IIS isn't mapped? (I ask because I just don't
know/understand)
(3) How do you map in IIS or see if the file is already mapped?
Thanks,
D
c_wigginton - 31 Jul 2007 20:51 GMT
There could be a cfmapping involved and that file in the inetpub/wwwroot is
using a cfinclude or a cftemplate tag. With a CF mapping, a cfinclude or
cftemplate tag can access cfm files in those mapped directories. CF doesn't
process other files such as css or image files and a direct path, URL wise,
does not exist to those files in cf mapped directories.
IIS is working because there is a web server connector installed that enables
the ColdFusion application server to proccess cfm pages.
Take a look at the Adobe Livedocs Mappings page
http://livedocs.adobe.com/coldfusion/7/htmldocs/00001709.htm#1162230
One way to configure the IIS would be to eliminate the Inetpub\wwwroot\AppName
folder and instead create a virtual directory that points to
C:\CFusionMX7\wwwroot\AppName with an alias of \AppName.
In any case, you're going to need to talk to your sys admin and configure IIS
correctly. There could be other configuration issues such as if it's in a
shared environment.