FP 2003 HowTo ASP pages?

[Bob Heitzman]

I cannot seem to create a web site that can run under http://localhost

My current web site http://www.slocleanair.org is temporairly hosted
on an Apache based site but it isn't behaving well. It was previously
running on an IIS host.

I have opened the old staging site from FP 2003 (still on IIS) via
HTTP as a remote site to a locally created empty web site. I have
"published" from the IIS site to my local disk.

I have tried creating a local empty web site under my \inetpub\wwwroot
where I have a few other sites running OK but FP 2003 doesn't want to
create a site there. I have created an empty web on the root of C:\
and FP was OK with that but I can't preview anything from that
location because (I assume) my site is made up of .asp pages.

I tried publishing from the C:\ site to a site under wwwroot but when
I try to open the pages I get an error 500.

I guess it all boils down to I haven't a clue how to manage an .asp
based web site using FP 2003 - is it just not possible? The site
doesn't use .asp features, I'm not sure why the site was created with
all .asp extensions for the web pages.

Any guidence on how to deal with .ASP using FP 2003?

TIA

 

[Jim Buyens]

Responses interspersed...

I cannot seem to create a web site that can run under
http://localhost

My current web site http://www.slocleanair.org is
temporairly hosted on an Apache based site but it isn't
behaving well. It was previously running on an IIS host.

Please define "not behaving well." What do you do, and what error message
results?

I have opened the old staging site from FP 2003 (still on
IIS) via HTTP as a remote site to a locally created empty
web site. I have "published" from the IIS site to my local
disk.

I have tried creating a local empty web site under my
\inetpub\wwwroot
where I have a few other sites running OK but FP 2003
doesn't want to create a site there.

Please define, "doesn't want." What command do you issue, and what error
message do you get?

I have created an empty web on the root of C:\
and FP was OK with that but I can't preview anything from
that location because (I assume) my site is made up
of .asp pages.

Please define, "can't preview." What happens?

I tried publishing from the C:\ site to a site under
wwwroot but when I try to open the pages I get an error
500.

I guess it all boils down to I haven't a clue how to
manage an .asp based web site using FP 2003 - is it just
not possible?

No, it usually works quite well.

The site doesn't use .asp features, I'm not sure why the
site was created with all .asp extensions for the web
pages.

Any guidence on how to deal with .ASP using FP 2003?

Personally, I would run Server Health in your local Web server, then open
the root Web and run Recalcualte Hyperlinks, then open the copy of your Web
that you *can* open and try publishing to a new web at
http://127.0.0.1/newweb or whatever.

But it's hard to say without knowing what those other error messages are.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Stefan B Rusynko]

PS
If the site has no ASP code in it, it shouldn't have .asp extensions
- extra unnecessary calls to the server
Rename the files to .htm




| Responses interspersed...
|
| "Bob Heitzman" wrote:
|
| > I cannot seem to create a web site that can run under
| > http://localhost
| >
| > My current web site http://www.slocleanair.org is
| > temporairly hosted on an Apache based site but it isn't
| > behaving well. It was previously running on an IIS host.
|
| Please define "not behaving well." What do you do, and what error message
| results?
|
| > I have opened the old staging site from FP 2003 (still on
| > IIS) via HTTP as a remote site to a locally created empty
| > web site. I have "published" from the IIS site to my local
| > disk.
| >
| > I have tried creating a local empty web site under my
| > \inetpub\wwwroot
| > where I have a few other sites running OK but FP 2003
| > doesn't want to create a site there.
|
| Please define, "doesn't want." What command do you issue, and what error
| message do you get?
|
| > I have created an empty web on the root of C:\
| > and FP was OK with that but I can't preview anything from
| > that location because (I assume) my site is made up
| > of .asp pages.
|
| Please define, "can't preview." What happens?
|
| > I tried publishing from the C:\ site to a site under
| > wwwroot but when I try to open the pages I get an error
| > 500.
| >
| > I guess it all boils down to I haven't a clue how to
| > manage an .asp based web site using FP 2003 - is it just
| > not possible?
|
| No, it usually works quite well.
|
| > The site doesn't use .asp features, I'm not sure why the
| > site was created with all .asp extensions for the web
| > pages.
| >
| > Any guidence on how to deal with .ASP using FP 2003?
|
| Personally, I would run Server Health in your local Web server, then open
| the root Web and run Recalcualte Hyperlinks, then open the copy of your Web
| that you *can* open and try publishing to a new web at
| http://127.0.0.1/newweb or whatever.
|
| But it's hard to say without knowing what those other error messages are.
|
| Jim Buyens
| Microsoft FrontPage MVP
| http://www.interlacken.com
| Author of:
| *----------------------------------------------------
| |\---------------------------------------------------
| || Microsoft Office FrontPage 2003 Inside Out
| ||---------------------------------------------------
| || Web Database Development Step by Step .NET Edition
| || Microsoft FrontPage Version 2002 Inside Out
| || Faster Smarter Beginning Programming
| || (All from Microsoft Press)
| |/---------------------------------------------------
| *----------------------------------------------------
|

 

[Jon Spivey]

Actually that's not true any more - it used to be a very valid point back in
the days of NT4 but win2k and 2003 are much smarter in this regard. There's
no harm atall in making every page in a site .asp - if nothing else it means
you have the option of adding asp code later without having to rename pages
or worse lose your search engine ranking.

 

[Jim Buyens]

I thought if that, but I was afraid the previous designer might
have used the .asp filename extension in order to get SSI processing.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Bob Heitzman]

I'm still working on: <...is temporairly hosted
on an Apache based site but it isn't behaving well...

from the original post...can you run ASP on Apache????

The pages are truly ASP pages, just HTML with some JavaScript for
navigation. There are a few server side includes that pull in the
JavaScript on each page.

http://www.slocleanair.org is the site - and it is running on an Apache
server at the moment.

I didn't create the site, just inherited it when the previous web host went
out of business.

I'll reply to the first reply next week.

 

[Bob Heitzman]

Responses interspersed...

Please define "not behaving well." What do you do, and what error message
results?

Includes not being honored consistantly. (partly due to security not
being set properly). Code page problems. Note that the current site is
a FTP copy of the old site with minor tweaks to get it to run on
Apache. The current site was not puvblished from FP2003. It may have
be "touched" with DreamWeaver. The goal is to get the site to a point
were FP2002/3 can be used to manage the site.

Please define, "doesn't want." What command do you issue, and what error
message do you get?

When I create an Empty Web at c:\Inetpup\wwwroot\testSite I get the
error:
"Unable to create a disk-based web at "c:\Inetpup\wwwroot\testSite"
becuase its parent Web would not be a disk-based Web. Create the
disk-based Wen elsewhere, outside...."

Problem is if I create the web outside the wwwroot my preview's do not
work correctly.

I populated the new "disk-based" web by opening my current staging
site:
http://slocleanair.eastaging.com as a remote site to my new web based
on the Empty Web template.

Note that the old site was managed using FP2000 (and on occasion
FP2002).

Please define, "can't preview." What happens?

I get an error that I must save or publish the web OR just the text of
the web page appears instead of the web page.

No, it usually works quite well.

What would the sequence of events be able to:

0 get a local copy of our old staging area
0 being able to see images while editing (properly resolved links)
0 being able to "preview in browser" with naviagation, includes and
images resolved properly
0 publish our new local staging area to a web host

Previously we used two web sites (staging link above) and we published
to the production site (gone) using FP2000/2. Editing, previews and
navigation worked fine. Note that we did not have a local copy -
perhaps we can do the same thing with FP2003?

I am thinking we need to find a new-new web host and pick one that
specifically supports Windows based webs. Any suggestions? Is
iPowerWeb a good choice?

Personally, I would run Server Health in your local Web server, then open
the root Web and run Recalcualte Hyperlinks, then open the copy of your Web
that you *can* open and try publishing to a new web at
http://127.0.0.1/newweb or whatever.

You lost me here. The localhost IIS is running on an XP Pro SP2
desktop, it isn't IIS on Windows Server 2003.

I haven't see the "Recalculate Hyperlinks" tool - where is that run
from?

Do I need to Publish to a localhost web in order to preview? Or is
that just a troubleshooting step? The lack of properly resolved image
links and non-working navigation is crippling the editing process.

Any attemps I have made recently to publish to a local web site have
resulted in pages that throw internal errors or security errors.

Maybe I should revert back to FP2002?

TIA