Why Publish?

  • Thread starter Thread starter John R. Baker
  • Start date Start date
J

John R. Baker

In the past I have always developed and maintained FrontPage sites on my
local hard disk, and then "published" them to a web server on the Internet.

Now I have been asked to work on an existing FrontPage site that only exists
on a web server. Work is done "in place" on the web server, and the site
does not need to be "published".

One problem I see with this method is that interim changes (doing a "<CTRL>
S") while working on a page will result in the surfing public being able to
view pages in an interim state. What other problems are there with this
method (in-place editing)?

Will new pages show up in all navigation bars?
Will FrontPage components (such as hit counters & forms) work right?
Any other concerns?

Thanks for your help!

- John R. Baker
 
See below

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================


John R. Baker said:
In the past I have always developed and maintained FrontPage sites on my
local hard disk, and then "published" them to a web server on the Internet.

Now I have been asked to work on an existing FrontPage site that only exists
on a web server. Work is done "in place" on the web server, and the site
does not need to be "published".

One problem I see with this method is that interim changes (doing a
Click to expand...
S") while working on a page will result in the surfing public being able to
view pages in an interim state. What other problems are there with this
method (in-place editing)?

Will new pages show up in all navigation bars?
Click to expand...
Yes if you add them.
Will FrontPage components (such as hit counters & forms) work right?
Click to expand...
Yes, you don't have to publish when working directly on a server with FP
extensions.
Any other concerns?
Click to expand...
Just that world see what you are doing, unless you publish the web to a
subweb, and then make your changes, then publish back to the root, which is
then just like work locally and publishing.
 
the fact that you're using yet another machine to do
something that could be done locally just seems to
make the process more complicated, and possibly
a little slower.

--
Grace + Peace,
Peter N Roth
Engineering Objects International
http://engineeringobjects.com
 
Another issue, whenever you save a page live it can cause a quick
recalculation of the web. This takes time and can eat up some server CPU
cycles. Live is great, especially if there are going to be a lot of people
editing, but it's easier to work with it locally instead so that any
mistakes that are made don't ruin the site. You can publish it back to your
computer also, just like you would publish it to a web site (if you're using
a local web server then you publish with http://localhost/webname otherwise
you enter the path you want the web to be stored at). Working live does have
the added benefit that you can be sure features will work on the server
because you are working directly against the server.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage
 
Back
Top