What is the best way to handle global includes for 3 subwebs that may at
various times consume similiar include files such as ENQUIRY FORMS.
I ask this question as I now have the oppportunity to control sub webs more
tightly on my new host via virtual director and wish to improve the folder
structure and code on my various sites.
However, I am concerned with the implications for the PHYSICAL and RELATIVE
file path options.
For instance, my host says I can use a physical root
m:\net\users\acc101\html\
....but I don't understand if this path changes the deeper you go into the
subwebs. For instance, will the FORM INCLUDE inside the /INCLUDES FOLDER:
eg <!--# virtual includes="m:\net\users\acc101\html\includes\form.I NC"-->
....always be written this way in code no matter where you are in the
subweb(s) folder structure or will I have to use some form of
server.variables to extract the
locaiton of the global include folder in the root and then re-write the
path.
I am also concerned with the testing implications on my local drive which
uses http://localhost/ ...It appears I would have to manually re-write the
paths when I take live.
I probably have not explained this clearly but I need help in working out
how to:
- consume global includes via my subwebs
- Which is better - relative or absolute - I am gravitating towards absolute
- Implications for local testing environment...I cannot use my host's root
path as it is different
Appreciate help!
Jason
