------_=_NextPart_001_01BE7483.9FAAB93A
Content-Type: text/plain;
charset="iso-8859-1"
Re-submitted: Hopefully, this time its _not_ in MIME format.
-------------------------------------------------------------
Using WO4 on Win NT running IIS
Problem: Server-side include declarations being ignored by IIS.
This problem is not directly a WO issue but is an issue indirectly.
I am building an addition to an existing (elaborate) web-site. The look and
feel for this site is predicated by files that are included by IIS based on
#include directives. The basic premise is as follows:
<!-- #include virtual="look_and_feel.inc" -->
The actual page content
When I built my "additions" using WO, I incorporated the look-and-feel using
a WOComponentContent.
Now, WO does its part when it builds the page and pre-pends the page with
the necessary include statements (as defined in my look and feel component).
However, IIS blows past the includes without resolving them.
All other pages for this site that are "published" using MS Front Page work
as expected. I know that the act of publishing writes to several hidden
folders as well. However, when using a WO application to generate pages in
real time, the publish metaphor doesn't apply.
Has anyone else had the occasion to do anything similar? With success?
I have even tried to use absolute reference to the inc files
(http://ip-address/look_and_feel.inc).
Any help is appreciated.
Sri
--------------------
Srivaths Sankaran
(813)971-3707 x292
mailto:[EMAIL PROTECTED]
------_=_NextPart_001_01BE7483.9FAAB93A
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2448.0">
<TITLE>WO and Server-side includes</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Re-submitted: Hopefully, this time its _not_ in MIME
format.</FONT>
<BR><FONT SIZE=2>-------------------------------------------------------------</FONT>
</P>
<BR>
<P><FONT SIZE=2>Using WO4 on Win NT running IIS</FONT>
</P>
<P><FONT SIZE=2>Problem: Server-side include declarations being ignored by
IIS.</FONT>
</P>
<P><FONT SIZE=2>This problem is not directly a WO issue but is an issue
indirectly.</FONT>
</P>
<P><FONT SIZE=2>I am building an addition to an existing (elaborate) web-site.
The look and</FONT>
<BR><FONT SIZE=2>feel for this site is predicated by files that are included by IIS
based on</FONT>
<BR><FONT SIZE=2>#include directives. The basic premise is as follows:</FONT>
</P>
<P><FONT SIZE=2><!-- #include virtual="look_and_feel.inc"
--></FONT>
<BR><FONT SIZE=2>The actual page content</FONT>
</P>
<P><FONT SIZE=2>When I built my "additions" using WO, I incorporated the
look-and-feel using</FONT>
<BR><FONT SIZE=2>a WOComponentContent.</FONT>
</P>
<P><FONT SIZE=2>Now, WO does its part when it builds the page and pre-pends the page
with</FONT>
<BR><FONT SIZE=2>the necessary include statements (as defined in my look and feel
component).</FONT>
<BR><FONT SIZE=2>However, IIS blows past the includes without resolving them.</FONT>
</P>
<P><FONT SIZE=2>All other pages for this site that are "published" using MS
Front Page work</FONT>
<BR><FONT SIZE=2>as expected. I know that the act of publishing writes to
several hidden</FONT>
<BR><FONT SIZE=2>folders as well. However, when using a WO application to
generate pages in</FONT>
<BR><FONT SIZE=2>real time, the publish metaphor doesn't apply.</FONT>
</P>
<P><FONT SIZE=2>Has anyone else had the occasion to do anything similar? With
success?</FONT>
</P>
<P><FONT SIZE=2>I have even tried to use absolute reference to the inc files</FONT>
<BR><FONT SIZE=2>(<A HREF="http://ip-address/look_and_feel.inc"
TARGET="_blank">http://ip-address/look_and_feel.inc</A>).</FONT>
</P>
<P><FONT SIZE=2>Any help is appreciated.</FONT>
</P>
<P><FONT SIZE=2>Sri</FONT>
</P>
<P><FONT SIZE=2>--------------------</FONT>
<BR><FONT SIZE=2>Srivaths Sankaran</FONT>
<BR><FONT SIZE=2>(813)971-3707 x292</FONT>
<BR><FONT SIZE=2><A
HREF="mailto:[EMAIL PROTECTED]">mailto:[EMAIL PROTECTED]</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01BE7483.9FAAB93A--
