Confused about server file matching in FP2003

[Guest]

Hi all...

Using FP2003, publishing files Local to Remote, rather than
maintaining the "golden copy" on the server alone.

In the Remote Web Site pane of FP2003, many files have the
Unmatched designation, even though I've freshly published them,
say as recently as a minute previously.

It may be relevant that in the Remote Web Site Props dialog,
I have set only the options

--Changed Pages Only
--Determine changes by comparing source and destination sites.
--Log changes during publish.


Question: why is this happening?

Related questions: I'm doing Local to Remote for two reasons.
-- I don't have constant broadband access, and often develop
the site offline.
-- I'm nervous about website hacking, and use FP's publish
feature as a write-only channel. Does this anxiety have
much (or any) basis in fact?
-- Even though I've entered the URL of the remote site in the
Remote Web Site Props dialog, the Tools>Server menu command
appears dimmed. Is this somehow due to the Local to Remote
strategy?

FYI, under Tools>Site Settings>General tab,
File location is the path to the local website,
FP Server Extensions version is 6.0.2.5516, which corresponds
to the Sharepoint extensions, right?
Server version field says "No server currently in use"
However, using the mysite.com/_vti_inf.htm-and-View-Source method,
the server is using version 5.0.2.2634


Uh, am I asking too many questions at once?

Most grateful,
MVSmith

 

[Jim Buyens]

-----Original Message-----

Hi all...
Howdy.

Using FP2003, publishing files Local to Remote, rather
than maintaining the "golden copy" on the server alone.

In the Remote Web Site pane of FP2003, many files have
the Unmatched designation, even though I've freshly
published them, say as recently as a minute previously.

It may be relevant that in the Remote Web Site Props
dialog, I have set only the options

--Changed Pages Only
--Determine changes by comparing source and destination
sites.
--Log changes during publish.

Question: why is this happening?

If the remote server is running the FrontPage Server
Extensions and you're publishing by http, try
recalculating hyperlinks on both sites.

If the remote server is running the FrontPage Server
Extensions and you're not publishing by http, start
publishing by http.

You also might want to try the procedure at:

FrontPage Publish Command Fails
http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=24

If the remote server isn't running the FrontPage Server
Extensions, I presume you're publishing by FTP. In that
case, the problem may be caused by a difference in time
zones between your PC and the remote site. Usually
FrontPage detects time zone differences and compensates,
but it does have trouble with FTP servers. I'm not aware
of a fix for this.

Related questions: I'm doing Local to Remote for two
reasons.
-- I don't have constant broadband access, and often
develop the site offline.

That's a good reason.

-- I'm nervous about website hacking, and use FP's
publish feature as a write-only channel. Does this
anxiety have much (or any) basis in fact?

Your anxiety is justified. People lose Web sites every
day, not only from hacking but from hard disk failures,
lightning strikes, and any number of problems at the host.

Nobody was ever sorry they had a backup.

-- Even though I've entered the URL of the remote site
in the Remote Web Site Props dialog, the Tools>Server
menu command appears dimmed. Is this somehow due to
the Local to Remote strategy?

No, but if your local site is disk-based, there's no
server to administer, and so the Tools, Server menu is
dimmed.

To administer the remote server, first you have to open
it.

Security isn't something you configure locally and then
publish. That's because the local site and the remote
site *ought* to have different security.

FYI, under Tools>Site Settings>General tab,
File location is the path to the local website,
FP Server Extensions version is 6.0.2.5516, which
corresponds to the Sharepoint extensions, right?
Server version field says "No server currently in
use" However, using the
mysite.com/_vti_inf.htm-and-View-Source method,
the server is using version 5.0.2.2634

I have a feeling that you're running a local Web server,
but opening your Web through the file system. For
example, you might be opening c:\inetpub\wwwroot.

Instead, you should open http://127.0.0.1. That's a
special address that always means "this computer".

Uh, am I asking too many questions at once?

Not necessarily.

Most grateful,
MVSmith

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)
|/---------------------------------------------------
*----------------------------------------------------