[wdvltalk] Re: Using #include

2003-12-03 Thread Brewnetty \(AuntySpam\)
I was under the impression that only shtml could load includes. Maybe one of our more knowledgeable list members can enlighten us both. AuntySpam, SLP Coordinator, pspug.org http://www.pspug.org/edu/edu.shtml http://www.pspug.org/edu/slp/assign.shtml

[wdvltalk] Re: Using #include

2003-12-03 Thread Scott Glasgow
in the standards body(ies) has recognized this as a desirable objective, eh? Cheers, Scott - Original Message - From: Brewnetty (AuntySpam) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 1:46 PM Subject: [wdvltalk] Re: Using #include I was under the impression

[wdvltalk] RE: Using #include

2003-12-03 Thread Linden, Todd
As Brewnetty stated, that will only work on .shtml files by default. If you are using a M$ server, you can set up IIS to parse all .htm files as .shtml files. To do this, open IIS. Right click on your website, select Properties. Go to the Home Directory tab, select the Configuration button

[wdvltalk] RE: Using #include

2003-12-03 Thread Scott Glasgow
PROTECTED] Sent: Wednesday, December 03, 2003 1:56 PM Subject: [wdvltalk] RE: Using #include As Brewnetty stated, that will only work on .shtml files by default. If you are using a M$ server, you can set up IIS to parse all .htm files as .shtml files. To do this, open IIS. Right click on your

[wdvltalk] Re: Using #include

2003-12-03 Thread Scott Glasgow
at the server. Cheers, Scott - Original Message - From: jac - WDVL [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 2:01 PM Subject: [wdvltalk] Re: Using #include http://websitetips.com/ssi/ Scott, this site has very good tuts on SSI's HTH jac -Original

[wdvltalk] RE: Using #include

2003-12-03 Thread Trusz, Andrew
If its a unix server, SSI will almost certainly be available. Either ask or test. drew -Original Message- From: Linden, Todd [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 1:57 PM To: [EMAIL PROTECTED] Subject: [wdvltalk] RE: Using #include As Brewnetty stated

[wdvltalk] Re: Using #include

2003-12-03 Thread Cheryl D. Wise
Depends on how the server is set-up. You can set it up to parse all pages but most web hosts will not do so due to the additional server overhead that causes. Another option is to use server side includes with asp, php or whatever your host supports. Cheryl D. Wise Certified Professional Web

[wdvltalk] RE: Using #include

2003-12-03 Thread Mark Groen
- Original Message - Sent: December 03, 2003 11:02 AM Subject: [wdvltalk] RE: Using #include Thanks, Todd. After a good deal more searching, I found this reference: http://www.webreference.com/programming/ssi/intro/ This confirms what you have said below. I'll have to check with my

[wdvltalk] RE: Using #include

2003-12-03 Thread Scott Glasgow
- Original Message - From: Mark Groen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 2:11 PM Subject: [wdvltalk] RE: Using #include - Original Message - Sent: December 03, 2003 11:02 AM Subject: [wdvltalk] RE: Using #include Thanks, Todd. After a good deal

[wdvltalk] Re: Using #include

2003-12-03 Thread Trusz, Andrew
-Original Message- From: Cheryl D. Wise Sent: Wednesday, December 03, 2003 12:56 PM To: [EMAIL PROTECTED] Subject: [wdvltalk] Re: Using #include Depends on how the server is set-up. You can set it up to parse all pages but most web hosts will not do so due to the additional server

[wdvltalk] RE: Using #include

2003-12-03 Thread Stephen Caudill
--- Scott Glasgow wrote: --- : I am revamping my site to use CSS only, no tables. In the : process, I thought that I would also avoid some of the repetition : of code for sidebar menus, etc. by using the !--#include : file=/sideinclude.html -- syntax to build the menu

[wdvltalk] RE: Using #include

2003-12-03 Thread Stephen Caudill
--- Stephen Caudill wrote: --- : Scott, : : You're barking up the right tree. You got references to those : other languages because most languages support some sort of : include directive. This is definitely something that has to be : processed by the server, though.