RE: Okay, bear with me, I'm not even sure what I'm asking...
Jeff, Using /images will always go to the domain root. If you have more than one site under the domain root like below, then doing /images in any of those sites will tell the browser to resolve to the images directory in www.domain.com. If you are interested in getting it to work for a particular site, you'll need to put /siteN/images where siteN refers to the site you are in. www.domain.com/site1 www.domain.com/site2 www.domain.com/site3 img src="" will draw from the images directory in www.domain.com img src="" will draw from the images directory in www.domain.com/site1/ etc HTH Paul [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Okay, bear with me, I'm not even sure what I'm asking...
Okay, here's the deal. One of our programmers has created an include that would be in the root of a site (call it, navbar.cfm) and there's one page (index.cfm) that calls it from the root (cfinclude template=navbar.cfm). Now, in navbar.cfm, there's a path to an image (let's say img src="" for instance). He's using absolute paths because he says slash images should always refer to the root and doesn't understand why he can't include that same file in a page one directory below (about/index.cfm) and it not work. In other words, when the page below (about/index.cfm) tries to reconcile the path, it's seeing the same path that the root page is seeing (img src="" and it's breaking it and not showing the image (so now, when you view source on the page, you see http://devserver.ourdomain.com/images/... and you should see http://devserver.ourdomain.com/ThisSite/images/...) . Now, our development server is set up on a smallish PC running IIS and the site (and all others in development) is set up under the webroot of the IIS server, so that when you're testing it, you simply go to http://devserver.ourdomain.com/ThisSite/ and you can see the root of ThisSite which is the directory ThisSite under webroot (C:\InetPub\wwwroot\ThisSite). Is a virtual directory what he's looking for? Is it a mapping issue? I admit, I'm fairly stupid when it comes to IIS issues and web server administration issues, and will readily admit that I'm no mapping wizard, so I hope I explained it correctly, but I'd love to be able to do this. [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Okay, bear with me, I'm not even sure what I'm asking...
Jeff, cfinclude paths are not related to the paths of the web server.You can in fact create arbitrary aliases for paths (mappings) that out of your web root altogether.CF always uses a path that is relative to the current template path. So if your developer is 1 directory below the root he would use ../blah.cfm.Again, don't let him even bring up the image paths and virtual directorys et al.The web server doesnt' control this at all.If he wants a mapping to root he can create one in CF admin (using /) and this is actually done by default - and it's fine if you are not on a shared server or you have control over the environment. But if you are on a shared server be careful because everyone can include from your directory now using the root mapping. savy? Mark A. Kruger, MCSE, CFG www.cfwebtools.com www.necfug.com http://blog.mxconsulting.com ...what the web can be! -Original Message- From: Jeff Small [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 10:55 AM To: CF-Talk Subject: Okay, bear with me, I'm not even sure what I'm asking... Okay, here's the deal. One of our programmers has created an include that would be in the root of a site (call it, navbar.cfm) and there's one page (index.cfm) that calls it from the root (cfinclude template=navbar.cfm). Now, in navbar.cfm, there's a path to an image (let's say img src="" for instance). He's using absolute paths because he says slash images should always refer to the root and doesn't understand why he can't include that same file in a page one directory below (about/index.cfm) and it not work. In other words, when the page below (about/index.cfm) tries to reconcile the path, it's seeing the same path that the root page is seeing (img src="" and it's breaking it and not showing the image (so now, when you view source on the page, you see http://devserver.ourdomain.com/images/... and you should see http://devserver.ourdomain.com/ThisSite/images/...) . Now, our development server is set up on a smallish PC running IIS and the site (and all others in development) is set up under the webroot of the IIS server, so that when you're testing it, you simply go to http://devserver.ourdomain.com/ThisSite/ and you can see the root of ThisSite which is the directory ThisSite under webroot (C:\InetPub\wwwroot\ThisSite). Is a virtual directory what he's looking for? Is it a mapping issue? I admit, I'm fairly stupid when it comes to IIS issues and web server administration issues, and will readily admit that I'm no mapping wizard, so I hope I explained it correctly, but I'd love to be able to do this. [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Okay, bear with me, I'm not even sure what I'm asking...
When you use /images/something.gif it takes your domain name (devserver.ourdomain.com) and appends that path to the end of it. So, in the example you gave, he should reference that image a /ThisSite/images/something.gif and then it will just tack that onto the end.That's an HTTP/browser thing, and has nothing to do with CF or where it's included from.It just matters based on where the main file that's being returned to the browser resides.You could just do images/something.gif (minus the leading slash) and it will look for an images folder in the same folder as where the main document that is being served to the browser resides.So if you have devserver.ourdomain.com/ThisSite/index.cfm and it's including something that's somewhere else on the server, you can just reference images/something.gif and it will look for the imagesfolder inside of ThisSite since that's where the index.cfm is.You could also do a virtual directory but it doesn't necessarily solve a whole lot. John Burns -Original Message- From: Jeff Small [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 11:55 AM To: CF-Talk Subject: Okay, bear with me, I'm not even sure what I'm asking... Okay, here's the deal. One of our programmers has created an include that would be in the root of a site (call it, navbar.cfm) and there's one page (index.cfm) that calls it from the root (cfinclude template=navbar.cfm). Now, in navbar.cfm, there's a path to an image (let's say img src="" for instance). He's using absolute paths because he says slash images should always refer to the root and doesn't understand why he can't include that same file in a page one directory below (about/index.cfm) and it not work. In other words, when the page below (about/index.cfm) tries to reconcile the path, it's seeing the same path that the root page is seeing (img src="" and it's breaking it and not showing the image (so now, when you view source on the page, you see http://devserver.ourdomain.com/images/... and you should see http://devserver.ourdomain.com/ThisSite/images/...) . Now, our development server is set up on a smallish PC running IIS and the site (and all others in development) is set up under the webroot of the IIS server, so that when you're testing it, you simply go to http://devserver.ourdomain.com/ThisSite/ and you can see the root of ThisSite which is the directory ThisSite under webroot (C:\InetPub\wwwroot\ThisSite). Is a virtual directory what he's looking for? Is it a mapping issue? I admit, I'm fairly stupid when it comes to IIS issues and web server administration issues, and will readily admit that I'm no mapping wizard, so I hope I explained it correctly, but I'd love to be able to do this. [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Okay, bear with me, I'm not even sure what I'm asking...
Jeff, The easiest way I see to fix this quickly (if you don't have multiple sites each running different image directories) is to make a mapping in the CFAdmin of /images pointing to the images directory. That should clear up the problem. Steve -Original Message- From: Jeff Small [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 11:55 AM To: CF-Talk Subject: Okay, bear with me, I'm not even sure what I'm asking... Okay, here's the deal. One of our programmers has created an include that would be in the root of a site (call it, navbar.cfm) and there's one page (index.cfm) that calls it from the root (cfinclude template=navbar.cfm). Now, in navbar.cfm, there's a path to an image (let's say img src="" for instance). He's using absolute paths because he says slash images should always refer to the root and doesn't understand why he can't include that same file in a page one directory below (about/index.cfm) and it not work. In other words, when the page below (about/index.cfm) tries to reconcile the path, it's seeing the same path that the root page is seeing (img src="" and it's breaking it and not showing the image (so now, when you view source on the page, you see http://devserver.ourdomain.com/images/... and you should see http://devserver.ourdomain.com/ThisSite/images/...) . Now, our development server is set up on a smallish PC running IIS and the site (and all others in development) is set up under the webroot of the IIS server, so that when you're testing it, you simply go to http://devserver.ourdomain.com/ThisSite/ and you can see the root of ThisSite which is the directory ThisSite under webroot (C:\InetPub\wwwroot\ThisSite). Is a virtual directory what he's looking for? Is it a mapping issue? I admit, I'm fairly stupid when it comes to IIS issues and web server administration issues, and will readily admit that I'm no mapping wizard, so I hope I explained it correctly, but I'd love to be able to do this. _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Okay, bear with me, I'm not even sure what I'm asking...
No, mappings in CF have nothing to do with the web path to the images directory.The mappings in CFAdmin only have to do with cfinclude, cfmodule, CFCs and CF related actions.img src.. is an HTTP thing and all of that is managed by your web server.You just have to remember that as far as the browser is concerned, one file is being called (no matter how many includes you're doing) and all of your img src... Tags need to have the right path when they're called by the main document, no matter how many includes are being called or where they're located on the server. John Burns -Original Message- From: DURETTE, STEVEN J (AIT) [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 1:43 PM To: CF-Talk Subject: RE: Okay, bear with me, I'm not even sure what I'm asking... Jeff, The easiest way I see to fix this quickly (if you don't have multiple sites each running different image directories) is to make a mapping in the CFAdmin of /images pointing to the images directory. That should clear up the problem. Steve -Original Message- From: Jeff Small [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 11:55 AM To: CF-Talk Subject: Okay, bear with me, I'm not even sure what I'm asking... Okay, here's the deal. One of our programmers has created an include that would be in the root of a site (call it, navbar.cfm) and there's one page (index.cfm) that calls it from the root (cfinclude template=navbar.cfm). Now, in navbar.cfm, there's a path to an image (let's say img src="" for instance). He's using absolute paths because he says slash images should always refer to the root and doesn't understand why he can't include that same file in a page one directory below (about/index.cfm) and it not work. In other words, when the page below (about/index.cfm) tries to reconcile the path, it's seeing the same path that the root page is seeing (img src="" and it's breaking it and not showing the image (so now, when you view source on the page, you see http://devserver.ourdomain.com/images/... and you should see http://devserver.ourdomain.com/ThisSite/images/...) . Now, our development server is set up on a smallish PC running IIS and the site (and all others in development) is set up under the webroot of the IIS server, so that when you're testing it, you simply go to http://devserver.ourdomain.com/ThisSite/ and you can see the root of ThisSite which is the directory ThisSite under webroot (C:\InetPub\wwwroot\ThisSite). Is a virtual directory what he's looking for? Is it a mapping issue? I admit, I'm fairly stupid when it comes to IIS issues and web server administration issues, and will readily admit that I'm no mapping wizard, so I hope I explained it correctly, but I'd love to be able to do this. _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Okay, bear with me, I'm not even sure what I'm asking...
Did I misunderstand this - I think he IS asking why he can't use cfinclude exaclty like he uses img... why img src="" works and why cfinclude template=/images/blah.cfm doesn't... right? I don't think he's asking how to use the image tag, I think he's asking how to get at the root using cfinclude - which IS germane to a cf mapping. -mk -Original Message- From: Burns, John D [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 12:56 PM To: CF-Talk Subject: RE: Okay, bear with me, I'm not even sure what I'm asking... No, mappings in CF have nothing to do with the web path to the images directory.The mappings in CFAdmin only have to do with cfinclude, cfmodule, CFCs and CF related actions.img src.. is an HTTP thing and all of that is managed by your web server.You just have to remember that as far as the browser is concerned, one file is being called (no matter how many includes you're doing) and all of your img src... Tags need to have the right path when they're called by the main document, no matter how many includes are being called or where they're located on the server. John Burns -Original Message- From: DURETTE, STEVEN J (AIT) [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 1:43 PM To: CF-Talk Subject: RE: Okay, bear with me, I'm not even sure what I'm asking... Jeff, The easiest way I see to fix this quickly (if you don't have multiple sites each running different image directories) is to make a mapping in the CFAdmin of /images pointing to the images directory. That should clear up the problem. Steve -Original Message- From: Jeff Small [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 11:55 AM To: CF-Talk Subject: Okay, bear with me, I'm not even sure what I'm asking... Okay, here's the deal. One of our programmers has created an include that would be in the root of a site (call it, navbar.cfm) and there's one page (index.cfm) that calls it from the root (cfinclude template=navbar.cfm). Now, in navbar.cfm, there's a path to an image (let's say img src="" for instance). He's using absolute paths because he says slash images should always refer to the root and doesn't understand why he can't include that same file in a page one directory below (about/index.cfm) and it not work. In other words, when the page below (about/index.cfm) tries to reconcile the path, it's seeing the same path that the root page is seeing (img src="" and it's breaking it and not showing the image (so now, when you view source on the page, you see http://devserver.ourdomain.com/images/... and you should see http://devserver.ourdomain.com/ThisSite/images/...) . Now, our development server is set up on a smallish PC running IIS and the site (and all others in development) is set up under the webroot of the IIS server, so that when you're testing it, you simply go to http://devserver.ourdomain.com/ThisSite/ and you can see the root of ThisSite which is the directory ThisSite under webroot (C:\InetPub\wwwroot\ThisSite). Is a virtual directory what he's looking for? Is it a mapping issue? I admit, I'm fairly stupid when it comes to IIS issues and web server administration issues, and will readily admit that I'm no mapping wizard, so I hope I explained it correctly, but I'd love to be able to do this. _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: Okay, bear with me, I'm not even sure what I'm asking...
- Original Message - From: Mark A. Kruger - CFG [EMAIL PROTECTED] To: CF-Talk [EMAIL PROTECTED] Sent: Thursday, March 25, 2004 2:36 PM Subject: RE: Okay, bear with me, I'm not even sure what I'm asking... Did I misunderstand this - I think he IS asking why he can't use cfinclude exaclty like he uses img... why img src="" works and why cfinclude template=/images/blah.cfm doesn't... right? I don't think he's asking how to use the image tag, I think he's asking how to get at the root using cfinclude - which IS germane to a cf mapping. Okay, see? I wasn't sure WHAT I was asking, but I knew I wasn't asking about using the image tag, lol. We've got several clients. They're all located this way. http://development.somedomain.com/client1/ http://development.somedomain.com/client2/ http://development.somedomain.com/client3/ And say, under client1/ (which is located at C://InetPub/wwwroot/client1/ logically) there are a couple of subdirectories (say client1/About/, client1/Contact/, client1/Products/, ) and for the index page in each directory, he'd like to use one include for footer/legal/link stuff in the root, or navigation include in the root (say for example Client1/navbar.cfm, and Client1/disclaimer.cfm) and in those directories, he wants to use absolute paths for the image directory in the root, so in his ONE include, he can say [src="" and it will work whether or not he's in the root, or in the lower (Products) directory. Make sense now? We'd like to have a mapping somehow for: http://development.somedomain.com/client1/ http://development.somedomain.com/client2/ http://development.somedomain.com/client3/ That would make it the root of each site so we could use cfincludes in that manner. Is a CF-Mapping what I'm looking for? [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Okay, bear with me, I'm not even sure what I'm asking...
The basic answer is: If you're talking about how to get the right path to use cfinclude... then you may need to set up a CF mapping. If you're talking about how to get an img src... to point to a certain location, then you need to base the location of the src="" on the location of the main file being called through the web address, _NOT_ the location of the included file. In you example, if your server is set up as such: http://development.somedomain.com/client1 And under client1, you have the following structure: client1 |_ about |_index.cfm |_ contact |_index.cfm |_ images |_something.gif |_ products |_index.cfm If someone navigates to http://development.somedomain.com/client1/about/index.cfm and you include a navbar.cfm in the page, you could reference the image in one of 2 ways.One would be img src=""> (which obviously won't be good when you move the site to www.client1.com because the image path will look for a folder called client1 in the root of the site and it won't find it)The better way to reference it would be img src="" which says to go one directory higher and then look for an images folder which is in the same place on either dev or live (1 directory higher).However, if there's an index.cfm in the client1 folder and it includes the navbar.cfm, neither approach will work on both servers.In that instance, you could create an images virtual directory and reference the images by /images/something.gif. I think the biggest problem is that you're handling 2 different kind of URLs.1 is a straight domains www.client1.com and one is a domain with a folder development.somedomain.com/client1.Your best bet would be to use http://client1.somedomain.com for development because then you can use the options above (most notably the /images/something.gif approach because no matter what directory you're in, or which server you're on, the images directory is always located in the root for that site. John Burns -Original Message- From: Jeff Small [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 2:56 PM To: CF-Talk Subject: Re: Okay, bear with me, I'm not even sure what I'm asking... - Original Message - From: Mark A. Kruger - CFG [EMAIL PROTECTED] To: CF-Talk [EMAIL PROTECTED] Sent: Thursday, March 25, 2004 2:36 PM Subject: RE: Okay, bear with me, I'm not even sure what I'm asking... Did I misunderstand this - I think he IS asking why he can't use cfinclude exaclty like he uses img... why img src="" works and why cfinclude template=/images/blah.cfm doesn't... right? I don't think he's asking how to use the image tag, I think he's asking how to get at the root using cfinclude - which IS germane to a cf mapping. Okay, see? I wasn't sure WHAT I was asking, but I knew I wasn't asking about using the image tag, lol. We've got several clients. They're all located this way. http://development.somedomain.com/client1/ http://development.somedomain.com/client2/ http://development.somedomain.com/client3/ And say, under client1/ (which is located at C://InetPub/wwwroot/client1/ logically) there are a couple of subdirectories (say client1/About/, client1/Contact/, client1/Products/, ) and for the index page in each directory, he'd like to use one include for footer/legal/link stuff in the root, or navigation include in the root (say for example Client1/navbar.cfm, and Client1/disclaimer.cfm) and in those directories, he wants to use absolute paths for the image directory in the root, so in his ONE include, he can say [src="" and it will work whether or not he's in the root, or in the lower (Products) directory. Make sense now? We'd like to have a mapping somehow for: http://development.somedomain.com/client1/ http://development.somedomain.com/client2/ http://development.somedomain.com/client3/ That would make it the root of each site so we could use cfincludes in that manner. Is a CF-Mapping what I'm looking for? [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Okay, bear with me, I'm not even sure what I'm asking...
Ok let's review: This:[src="" not include anything in the page processing.Instead it generates a separate http request AFTER the page is downloaded to the browser. That second request goes to: http://*whateverMyDomainIsCalled*.com/images/image1.jpg This:[cfinclude template = Client1/navbar.cfm]gets executed BEFORE the page is sent to the browser and actually RUNS the code in the file at: c:\*whateverTheCURRENTtemplateDirectoryIs*\Client1\navbar.cfm So if you want to include something from the root which is at: c:\wwwdocs\Client1\ And the template CALLING the included code is in C:wwwdocs\Client1\legal\ and you use cfinclude template=/client1/navbar.cfm the server first looks to see if there is a mapping for / in the cf settings.If there is no mapping for /, it then looks to see if there is a directory (a folder) called /client1 in directory (folder) containing the Calling template (the one in /legal/).It never actually looks at the root of the WEBSITE because CF has no knowledge of those settings IIS hands a request to CF, CF fills a buffer with stuff to send back and hands it back to IIS. That's how it works. In the scenario that you present, and assuming you are using the default installation of CF, if you tried: cfincldue tamplate=/client1/navbar.cfm (what's a tamplate?) the web server would try to include from the / mapping - usually the default web site directory - like inetpub/wwwdocs.If your web site is NOT the default web site on the server, or if the mapping has been removed (maybe a good idea on a shared server), then you will throw an error. If you tried cfinclude template =client1/navbar.cfm from the /legal/ directory - it would be looking for: c:\*whateverTheCURRENTtemplateDirectoryIs*\legal\Client1\navbar.cfm again it would fail. There are only 2 ways to to call a file using CFINCLUDEfrom (for example) c:\sites\mywebsites\client1\legal that resides in c:\sites\mywebsites\client1\ 1)use the ubiquitous 2 periods to move back one dir cfinclude template=../client1 B)Create a mapping in the cf administrator to use.For example, if you created a mapping called /bob/ that pointed to c:\sites\mywebsites\client1\ you could do cfinclude template=/bob/navbar.cfm and it would work.. although it might be a tradmark infringement. I hope this helps. Mark -Original Message- From: Jeff Small [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 1:56 PM To: CF-Talk Subject: Re: Okay, bear with me, I'm not even sure what I'm asking... - Original Message - From: Mark A. Kruger - CFG [EMAIL PROTECTED] To: CF-Talk [EMAIL PROTECTED] Sent: Thursday, March 25, 2004 2:36 PM Subject: RE: Okay, bear with me, I'm not even sure what I'm asking... Did I misunderstand this - I think he IS asking why he can't use cfinclude exaclty like he uses img... why img src="" works and why cfinclude template=/images/blah.cfm doesn't... right? I don't think he's asking how to use the image tag, I think he's asking how to get at the root using cfinclude - which IS germane to a cf mapping. Okay, see? I wasn't sure WHAT I was asking, but I knew I wasn't asking about using the image tag, lol. We've got several clients. They're all located this way. http://development.somedomain.com/client1/ http://development.somedomain.com/client2/ http://development.somedomain.com/client3/ And say, under client1/ (which is located at C://InetPub/wwwroot/client1/ logically) there are a couple of subdirectories (say client1/About/, client1/Contact/, client1/Products/, ) and for the index page in each directory, he'd like to use one include for footer/legal/link stuff in the root, or navigation include in the root (say for example Client1/navbar.cfm, and Client1/disclaimer.cfm) and in those directories, he wants to use absolute paths for the image directory in the root, so in his ONE include, he can say [src="" and it will work whether or not he's in the root, or in the lower (Products) directory. Make sense now? We'd like to have a mapping somehow for: http://development.somedomain.com/client1/ http://development.somedomain.com/client2/ http://development.somedomain.com/client3/ That would make it the root of each site so we could use cfincludes in that manner. Is a CF-Mapping what I'm looking for? [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Okay, bear with me, I'm not even sure what I'm asking...
John's suggestion is good, and you might also see if using a BASE HREF tag might help you. http://coveryourasp.com/BaseHref.asp Conan At 02:54 PM 3/25/2004, you wrote: I think the biggest problem is that you're handling 2 different kind of URLs.1 is a straight domains www.client1.com and one is a domain with a folder development.somedomain.com/client1.Your best bet would be to use http://client1.somedomain.com for development because then you can use the options above (most notably the /images/something.gif approach because no matter what directory you're in, or which server you're on, the images directory is always located in the root for that site. John Burns [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Okay, bear with me, I'm not even sure what I'm asking...
Yeah, I thought of that, but I am not aware of how compatible the BaseHref option is.I just don't use it soI don't know if it's an IE thing or all browsers.Anyway, I think the whole thing comes down to the domain.com/client1 thing vs. the client1.domain.com thing as well. I've played with that before and it's quite annoying. John Burns -Original Message- From: Conan Saunders [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 4:09 PM To: CF-Talk Subject: RE: Okay, bear with me, I'm not even sure what I'm asking... John's suggestion is good, and you might also see if using a BASE HREF tag might help you. http://coveryourasp.com/BaseHref.asp Conan At 02:54 PM 3/25/2004, you wrote: I think the biggest problem is that you're handling 2 different kind of URLs.1 is a straight domains www.client1.com and one is a domain with a folder development.somedomain.com/client1.Your best bet would be to use http://client1.somedomain.com for development because then you can use the options above (most notably the /images/something.gif approach because no matter what directory you're in, or which server you're on, the images directory is always located in the root for that site. John Burns [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: Okay, bear with me, I'm not even sure what I'm asking...
base href is money. Its not a browser thing it's an HTML thing. Been around atleast since HTML 3.2. -adam -Original Message- From: Burns, John D [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 09:46 PM To: 'CF-Talk' Subject: RE: Okay, bear with me, I'm not even sure what I'm asking... Yeah, I thought of that, but I am not aware of how compatible the BaseHref option is.I just don't use it soI don't know if it's an IE thing or all browsers.Anyway, I think the whole thing comes down to the domain.com/client1 thing vs. the client1.domain.com thing as well. I've played with that before and it's quite annoying. John Burns -Original Message- From: Conan Saunders [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 4:09 PM To: CF-Talk Subject: RE: Okay, bear with me, I'm not even sure what I'm asking... John's suggestion is good, and you might also see if using a BASE HREF tag might help you. http://coveryourasp.com/BaseHref.asp Conan At 02:54 PM 3/25/2004, you wrote: I think the biggest problem is that you're handling 2 different kind of URLs.1 is a straight domains www.client1.com and one is a domain with a folder development.somedomain.com/client1.Your best bet would be to use http://client1.somedomain.com for development because then you can use the options above (most notably the /images/something.gif approach because no matter what directory you're in, or which server you're on, the images directory is always located in the root for that site. John Burns [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
