Publishing without all those control/config files

[Ken Leonard]

Howdy;

I use FP2000 to build several web sites on servers with FrontPage
Extensions.

And, now, I am about to start a new site on a server, with limited
file space, which does not provide FrontPage Extensions.

So there's no need to publish all of the control files (vti.umpty.etc)
for the new site to the server. (They take up a heck of a lot of
space.)

How can I convince FP2000 to not publish all the overhead?

Thanx,
Ken

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Ken Leonard
(e-mail address removed) [Edit it to make it work.]

 

[Thomas A. Rowe]

FP never publish the _vti files between servers.

When you publish to a server that has the FP extensions, the extensions on
that specific server creates and maintains the _vti folder.

When you publish to a server that doesn't have the FP extensions via FP, the
_vti are not publish, nor are they needed. However you will need to keep
them in your local copy, which allows FP to manage the local version of the
web.

--

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

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

 

[Ken Leonard]

Tom;

Thanx for the reply.

But now I have another question: How does FP2000 know that the server
does not have FP Extensions?

Regardz,
Ken

FP never publish the _vti files between servers.

When you publish to a server that has the FP extensions, the extensions on
that specific server creates and maintains the _vti folder.

When you publish to a server that doesn't have the FP extensions via FP, the
_vti are not publish, nor are they needed. However you will need to keep
them in your local copy, which allows FP to manage the local version of the
web.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Ken Leonard
(e-mail address removed) [Edit it to make it work.]

 

[Thomas A. Rowe]

It checks for two hidden files in the root of the web it is trying to open
or publish to.

--

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

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

Tom;

Thanx for the reply.

But now I have another question: How does FP2000 know that the server
does not have FP Extensions?

Regardz,
Ken

FP never publish the _vti files between servers.

When you publish to a server that has the FP extensions, the extensions on
that specific server creates and maintains the _vti folder.

When you publish to a server that doesn't have the FP extensions via FP, the
_vti are not publish, nor are they needed. However you will need to keep
them in your local copy, which allows FP to manage the local version of the
web.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Ken Leonard
(e-mail address removed) [Edit it to make it work.]

 

[Stefan B Rusynko]

IMHO use a 3rd party FTP for more flexibility

In FP Publish to a top level root folder - say C:\MyFTP
In Windows Explorer search and delete all _vt* files and folders from C:\MyFTP
The use your FTP client
(or depending on the FTP client software you could set it up to never transfer any *_vt)




| Tom;
|
| Thanx for the reply.
|
| But now I have another question: How does FP2000 know that the server
| does not have FP Extensions?
|
| Regardz,
| Ken
|
| Thu, 4 Sep 2003 23:16:12 -0400, "Thomas A. Rowe" <[email protected]>
| wrote:
|
| >FP never publish the _vti files between servers.
| >
| >When you publish to a server that has the FP extensions, the extensions on
| >that specific server creates and maintains the _vti folder.
| >
| >When you publish to a server that doesn't have the FP extensions via FP, the
| >_vti are not publish, nor are they needed. However you will need to keep
| >them in your local copy, which allows FP to manage the local version of the
| >web.
|
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
| Ken Leonard
| (e-mail address removed) [Edit it to make it work.]