I've run into similar issues with our multilingual site, and the solution I
took is using wrapper files that set some variables to and then include the
index.cfm from the main application directory.
The coolest was the later conversion to a generic wrapper file which breaks
up it's name (or in your case the directory name) then sets it into request
scope variables and calls index.cfm
What this means is that you always have the same wrapper file and just it's
name (or location) defines what it will do.
For example:
<!--- Name: Generic Wrapper page
Description: Takes filename and based on it calls the index file with
correct language and action
Parameters:
written: 15/07/1999 NB
--->
<CFSET variables.TemplateName = GetFileFromPath(GetCurrentTemplatePath())>
<CFSET request.DisplayLanguage = listFirst(variables.TemplateName, "_")>
<CFSET attributes.FuseAction = listGetAt(variables.TemplateName, 2, "_.")>
<CFINCLUDE template="../index.cfm" >
in your case just change it to strip out the directory name (company name)
and based on that later on you can include graphics and whatever from the
correct directory (that's what we do for different languages).
HTH,
Noam
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
