Well, Since you have access to the root of the subdomain, you can create your own application.cfm for your application. For that matter any directory can have its own application.cfm (though that would be an extreme use of it). If you are unfamiliar with the concept of using something like application.cfm, just read up one of the excellent references to CF. Or google it.
George On 5/3/05, daniel kessler <[EMAIL PROTECTED]> wrote: > I don't *think* that I have access to the application.cfm file. I'm in a > shared hosting environment where our OIT staff has given me a sub-domain to > work from (hhp.umd.edu), so they probably have the access to the > application.cfm file. I don't see one in my file structure. > > > I agree with Rebecca and Pascal, this would be a better approach. As > > for using dreamweaver, I generally prefer to look after my own paths > > to files rather than letting a program do that. For that matter I > > really don't like using WYSIWYG editors like dreamweaver or frontpage, > > just for that reason, I have always used Homesite. > > > > On top of doing the include file in your Application.cfm, in Rebecca's > > example you can use the CGI.SERVER_NAME variable and use a CFIF > > statement to set the variables for each server. > > > > > I use a similar approach except that we keep the directory structure > > > > > for our applications the same on the prod and dev server, then use > > CGI. > > > Server_Name in the app_server.cfm file to make the request vars work > > > > > on any server. > > > > > > >In the application.cfm, you can set a variable that holds the > > > absolute > > > >path to the image folder (or the path starting from the root). Then > > > > > use > > > >that variable when you need the path to an image. I usually create > > a > > > >structure that holds parameters that depend on the server. > > Something > > > >like: > > > > > > > >request.app.dsn > > > >request.app.imgFolder > > > >request.app.rootFolder > > > >request.app.rootUrl > > > >request.app.mapping > > > >... > > > > > > > >I create them in a separate file that I include in the application. > > > > > cfm. > > > >I have a different file for every server (local, dev, staging, prod, > > > > > >...) where the application is deployed. > > > > > > > >> -----Original Message----- > > > >> From: daniel kessler [mailto:[EMAIL PROTECTED] > > > >> Sent: 03 May 2005 15:22 > > > >> To: CF-Talk > > > >> Subject: RE: level 1, level 2 > > > >> > > > >> Wouldn't /images/ refer to the images directory on the root > > level? > > > >This > > > >> is a directory within and the whole site is there. > > > >> > > > >> In what way would I define a variable for a path to the images. > > > > > It > > > >would > > > >> seem to me that the variable would have to change just like the > > > >header. > > > >> Can you give me a small example? sorry to be dense about it. > > > >> > > > >> >/images/ ?? or define a variable with the path to images. > > > >> > > > > >> >Pascal > > > >> > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:205414 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
