PWS getting finicky... (Full Version)

All Forums >> [Web Development] >> Server Issues



Message

bobby -> PWS getting finicky... (7/6/2002 16:58:11)

Anyone else ever experience this?

I run Win NT 4 w/ service pack 6 and PWS...

I haven' t had any troubles (since I figured out how to get it to work...) but now on a new site that I' m working on, PWS isn' t parsing my (SSI) include pages.

I' m using the exact same protocol as previous successful webs, but no joy this time around.

Any idea why PWS would suddenly stop parsing for includes on .shtml pages?






Mike54 -> RE: PWS getting finicky... (7/6/2002 17:15:10)

Bobby,

You' re using PWS and not IIS?
It' s not anything I' ve run into but have you changed any (very) subtle settings lately (you know, things that shouldn' t have any effect [;)])?



bobby -> RE: PWS getting finicky... (7/6/2002 17:20:28)

LOL!

Well, this IS Windows we' re talking about!

No, no IIS allowed (took me forever to get them to load PWS for me... I' m the " Webmaster" and it took me two years to get Internet access at my terminal!!!)

I haven' t changed anything, and the other webs are still working just fine... I can' t figure out what the deal is...

maybe I' ll try starting over... fortunately I only got as far as the CSS and one page into it before I discovered the flaw...

I did create the web on the network, then copy it to my Inetpub/wwwroot file to preview... maybe I need to start the web there... I' ll see if that helps.



bobby -> RE: PWS getting finicky... (7/6/2002 17:25:12)

Well, that didn' t do anything...

This is how the browser is returning the page... 

<link rel=" stylesheet"  type=" text/css"  href=" NeoStyles.css"  />

</head>

<body>
<!--#Include File=" includes/neonav.shtml"  -->

<hr />

<p> test  </p>

<hr />

</body>


It just isn' t parsing for the includes... I even tried changing the included file to " ../includes/neonav.shtml" -->

Still no luck...



Mike54 -> RE: PWS getting finicky... (7/6/2002 17:34:16)

OK maybe a stupid question but have you tried the full path? I know it shouldn' t matter but...



bobby -> RE: PWS getting finicky... (7/7/2002 14:25:08)

It hasn' t mattered before, but I' ll give that a shot Monday morning... anything is worth a try at this point.

BTW - the gods must be smiling on me... I' ve convinced them to send me the NT server disc so I can load IIS on our network server!!!

I told them it was for an intranet, so I' ll throw that on there and then I' ll be able to test on IIS instead of PWS... hopefully I get the disc and login info this year!!!
[&:]



Mike54 -> RE: PWS getting finicky... (7/7/2002 15:17:16)

I guess I' ve been lucky, I inherited a couple of older NT servers to work with so I don' t get any interference on how I play with them. I can assure you the " official" MIS guys wouldn' t me doing anything with the real network server. [:D]



Gil -> RE: PWS getting finicky... (7/7/2002 16:53:40)

bobby, this code looks wierd to me:

<link rel=" stylesheet" type=" text/css" href=" NeoStyles.css" />
</head>
<body> <!--#Include File=" includes/neonav.shtml" -->
<hr />
<p> test </p>
<hr />
</body>

Why is the included page a .shtml?

What is <hr /> ?I know what <hr> is.

I gues since I always use a .txt file for the included content anything else looks strange?



Doug G -> RE: PWS getting finicky... (7/7/2002 18:51:58)

quote:

What is <hr /> ?I know what <hr> is.

Compliance with the new xhtml 1.0 standard (the successor to html 4.01) requires closing tags for all elements. <hr /> , <br /> will " close" elements that never had a closing tag before. Everything' s needs to be lowercase, too, and attribute values must be quoted.

http://www.w3.org/MarkUp/



Gil -> RE: PWS getting finicky... (7/7/2002 19:22:23)

Yeah Doug, I realized the XHTML syntax, but didn' t see the DTD, so didn' t realize it was a XHTML doc. So far I' ve only used XML, not XHTML, so used the <hr></hr> syntax.I should play with the XHTML stuff some [:)]



bobby -> RE: PWS getting finicky... (7/9/2002 1:12:48)

This page is only html... just getting myself used to the " new" standard of closing those " non-closing" tags. It renders just fine this way, so I' m practicing. Still in the very early stages of layout as well, not really going for functionality... just getting my " template" set up the way I want it.

The .shtml extension is automatically parsed by the server (along with .asp) for includes, so that' s why I' m using that extension... just keeps things easier durring this stage to use the same extension on my includes as well.



bobby -> RE: PWS getting finicky... (7/9/2002 10:46:36)

Well... I think something is screwy...

I' ve tried using the full file path for my included page. Also tried chanign File to Virtual - just in case.

Also tried changing the .shtml extension on the page to .asp - to see if that would make a difference... still no dice.

I even tried changing the include file to a .txt - nada.

I also tried starting the web completely over again... still having the same troubles.

The part that really gets me, is that I have another web on this machine, in the same wwwroot directory, that uses seven different included pages and ASP with no problem.

I' m able to pull that web up and everything looks great.

I' m going to try one last time to see if I can get it to work... if not I' m going to tell them that I NEED IIS on the network to finish this project. Since it' s for a new product launch this summer, I expect they' ll let me have it sooner.

Still open to ideas, tho.
[:' (]



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.078125