The "Web server root" mentioned in the help files is what you're seeing: "d:\inetpub". This should change as you move the application from one Web server to another automatically.
Personally, I use <@INCLUDE "../includes/whatever.txt"> to get to a folder one level 'above' the Web root where I keep all these kinds of files. Jon -----Original Message----- From: Trevor Green [mailto:[EMAIL PROTECTED]] Sent: 12 August 2002 12:53 To: Multiple recipients of list witango-talk Subject: RE: RE: Witango-Talk: problem with <@INCLUDE> Hi Jon The help files on the tag states "The FILE attribute is a slash-separated path from the Web server root. The FILE attribute may include literal text, meta tags, or both". In my case I have FILE="<@var application$rootfilepath>menus/software/software-list.html ". The <@var application$rootfilepath> is set to <@APPFILEPATH> when the default.taf is run from for this particular application (because I develop on an XP box and when I develop I have to have my different Witango applications running off virtual directories to begin with). So, for example in this particular case the path "<@var application$rootfilepath>menus/software/software-list.html" equates to "/admin/menus/software/software-list.html". On the production server where there is no other application running it equates to "/menus/software/software-list.html". Where software is a vitual directory (and points somewhere else on the server and is really hidden from the Application server. However, I see what is happening. The T2K AS seems to be appending a d:\inetpub to the FILE= path so the file path is not off the root of the web application as I had thought (i.e. creating the virtual directory does nothing). Although "d:\inetpub\@@application$rootfilepath" does indeed point to my applications directory, I do not know where it is getting the "d:\inetpub" from. Is this a modifiable parameter? I can actually navigate to the correct directory using file="../../other directory/software/software-list.html" but would prefer a smarter solution in case I decide to change my directory structure at a later stage. Any recommendations? Regards Trevor -----Original Message----- From: Jon Grieve [mailto:[EMAIL PROTECTED]] Sent: 12 August 2002 01:23 PM To: Multiple recipients of list witango-talk Subject: RE: Witango-Talk: problem with <@INCLUDE> Trevor, I think you'll find that the path Tango is using for the include already includes a top-level path. So, it is in fact trying to look somewhere like "C:\INETPUB\WWWROOT\C:\yourpath..." If you turn on Debug mode for that TAF, I think you'll see exactly where it is looking. I believe this will change in the new version... Jon -----Original Message----- From: Trevor Green [mailto:[EMAIL PROTECTED]] Sent: 12 August 2002 12:17 To: Multiple recipients of list witango-talk Subject: Witango-Talk: problem with <@INCLUDE> I am using W2K, T2K (sorry WiT2K), IIS I have the following code: <@include file="<@var application$rootfilepath>menus/software/software-list.html"> The snag is that software-list.html is another directory somewhere else on the server. I have created a virtual directory under menus which references the correct directory where this file located. >From my web-browser, if point it to that file using that directory path it works fine. If I create a directory "software" (under menus) and copy the file there it works. It will not work (as I think I have discovered) when there is a virtual directory in the path. Is this correct? Is the only way to include that file to read in the contents into a variable using a file-read action? Trevor Green ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
