Recovering from ISP's Server move - Shared Borders

[DSG]

Windows XP Pro SP2 Version 2002
FrontPage 2000 4.0.2.6625 which has been adopted by Office 2000 (9.0.6926
SP3)

My ISP has just moved to a newer, larger server. It also hosts one of my
FrontPage Webs. When that happened, the Shared borders on the remote web
(top, left, bottom) did not transfer (they said), my password stopped
working, and Windows firewall is now blocking FrontPage from the internet,
meaning I can't publish all pages to refresh the remote site and get the
shared borders back.

I just found On About FrontPage, there is a button for Network Test. Which I
decided to investigate. I gives a dialog labeled FrontPage TCP/IP Test, and
lists
32 Bit Winsock, 127.0.0.1, Host Name, IP Address, localhost

As soon as the results appeared, nicely, Windows firewall dialog opens and
asks if I want to keep blocking this program: Microsoft FrontPage TCP/IP
Tester. I unblock it, and find that FrontPage.exe is no longer allowed to go
to the Internet. I add the program, and I should be able, now, to publish
with my new password.

Here is a problem I didn't expect. In looking at all the internal reports on
my local FrontPage app, I see that the ISP's move to the new server unlinked
the shared borders (top, bottom, left) (plus 73 other files I will be able
to fix myself). The shared borders look fine in the local FrontPage, but in
View > Reports, they are "unlinked files" meaning that I can't, yet, publish
until they are linked to something.

The top border has the navigation bar for the 8 main sections to the web and
a graphic background.
The left border holds a graphic background, and an icon that hyperlinks to a
remote web
The bottom border contains the copyright statement

So if they look fine in the local web, how and what do I link the shared
borders to, to get them to the remote web when I publish? Or do I just
publish?

 

[Ronx]

If your local site appears to be working and is up to date, I would
publish to the server using Publish All Files.
This will overwrite the existing site, and correct the shared borders
problems. It will also resynch the sites - it is probable that if you
tried publishing using Changed Files Only, every file would show as
being in conflict.

Before publishing, make sure any databases, hit counter files, form
results files are marked as "Do Not Publish" unless you wish to
overwrite these on the server.

 

[Corey Bryant]

Chances are, they just copied everything. This is the wrong way to move a
Frontpage website. A frontpage website needs to be published...

You should first synchronize all the files on the server. And then if the
company wants to, move only the data files (no _vti_cnf files). Then extend
the website with FPSE on the new server and publish.

 

[DSG]

Would you believe! After being away for 10 months, I had to unpack my
External Drive this morning for a support project tomorrow and there I have
two "published" versions of my most recent changes!

Friends - Have you published a backup lately?

And thanks to those of you who give your time to get us out of our jams.
DSG
.................
: Chances are, they just copied everything. This is the wrong way to move a
: Frontpage website. A frontpage website needs to be published...
:
: You should first synchronize all the files on the server. And then if the
: company wants to, move only the data files (no _vti_cnf files). Then
extend
: the website with FPSE on the new server and publish.
:
: --
: Corey R. Bryant
: http://www.loudcommerce.com/ | http://www.loudvoicesystem.com/ |
: http://www.mymerchantaccountblog.com/
:
:
: "DSG" wrote:
:
: > Windows XP Pro SP2 Version 2002
: > FrontPage 2000 4.0.2.6625 which has been adopted by Office 2000
(9.0.6926
: > SP3)
: >
: > My ISP has just moved to a newer, larger server. It also hosts one of my
: > FrontPage Webs. When that happened, the Shared borders on the remote web
: > (top, left, bottom) did not transfer (they said), my password stopped
: > working, and Windows firewall is now blocking FrontPage from the
internet,
: > meaning I can't publish all pages to refresh the remote site and get the
: > shared borders back.
: >
: > I just found On About FrontPage, there is a button for Network Test.
Which I
: > decided to investigate. I gives a dialog labeled FrontPage TCP/IP Test,
and
: > lists
: > 32 Bit Winsock, 127.0.0.1, Host Name, IP Address, localhost
: >
: > As soon as the results appeared, nicely, Windows firewall dialog opens
and
: > asks if I want to keep blocking this program: Microsoft FrontPage TCP/IP
: > Tester. I unblock it, and find that FrontPage.exe is no longer allowed
to go
: > to the Internet. I add the program, and I should be able, now, to
publish
: > with my new password.
: >
: > Here is a problem I didn't expect. In looking at all the internal
reports on
: > my local FrontPage app, I see that the ISP's move to the new server
unlinked
: > the shared borders (top, bottom, left) (plus 73 other files I will be
able
: > to fix myself). The shared borders look fine in the local FrontPage, but
in
: > View > Reports, they are "unlinked files" meaning that I can't, yet,
publish
: > until they are linked to something.
: >
: > The top border has the navigation bar for the 8 main sections to the web
and
: > a graphic background.
: > The left border holds a graphic background, and an icon that hyperlinks
to a
: > remote web
: > The bottom border contains the copyright statement
: >
: > So if they look fine in the local web, how and what do I link the shared
: > borders to, to get them to the remote web when I publish? Or do I just
: > publish?
: >
: >
: >
: >

 

[Ronx]

Restore the backup: Open the latest backup in FrontPage, then
File->Publish Site and type in (or browse to) the original location on
your PC.
Then Open and Publish the original website as usual.
Make sure (in both cases) you Publish all files, and watch out for form
results files that you may not wish to overwrite - mark these as "Don't
Publish"
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.

http://www.rxs-enterprises.org/fp

 

[Corey Bryant]

I work locally so I always have a copy. My business partner emails me when
he makes changes and then I will go that copy.