Remote and Local sites are the same... problem!

[Guest]

Hello Pros:

Need your help.

I use FrontPage 2003.

Recently I published "live," per the instructions I was given, in order to
password protect my site -- two folders (sub-sites).

Everything seemed to go smoothly until I attempted to make some changes and
publish. I was greeted, "quite rudely," with a message that stated that both
the local and remotes sites were the same, thus I could not publish, nor
could I "reverse" publish, remote to local.

I have checked everywhere I could think of, but I could not find any way to
correct this conflict.

I'm sure it will be quite obvious to you, and you will wonder why I couldn't
see the solution, but I need your help. I've drawn a blank, especially in
that I was following someone else's procedure.

For the record, consequetly, all of the subsequent changes/updates I have
made, to my site in FrontPage, are actually being made directly on the remote
site... and password protect does work. Btw, the procedure enabled me to
password protect in FrontPage (as the creator said, "The FrontPage way!").
Prior to this I had tried to use the hosting service's Control Panel/utility
only to have htaccess and FrontPage Extensions corrupted each time the user
names and passwords were added or deleted, or when FrontPage Extensions had
to be reinstalled.

As I mentioned, password protection is working, but now I have the conflict
of the local and remote sites being one in the same.

I'm feeling a little stupid, at this moment... so please help!

Thanks,

Patrick

 

[Tom Willett]

If you are actually making the changes on the live remote site, you can't
publish. It's already there. You just save the page(s) you're working on.
--
===
Tom Willett
Microsoft MVP - FrontPage
---
FrontPage Support:
http://www.frontpagemvps.com/
===
| Hello Pros:
|
| Need your help.
|
| I use FrontPage 2003.
|
| Recently I published "live," per the instructions I was given, in order to
| password protect my site -- two folders (sub-sites).
|
| Everything seemed to go smoothly until I attempted to make some changes
and
| publish. I was greeted, "quite rudely," with a message that stated that
both
| the local and remotes sites were the same, thus I could not publish, nor
| could I "reverse" publish, remote to local.
|
| I have checked everywhere I could think of, but I could not find any way
to
| correct this conflict.
|
| I'm sure it will be quite obvious to you, and you will wonder why I
couldn't
| see the solution, but I need your help. I've drawn a blank, especially in
| that I was following someone else's procedure.
|
| For the record, consequetly, all of the subsequent changes/updates I have
| made, to my site in FrontPage, are actually being made directly on the
remote
| site... and password protect does work. Btw, the procedure enabled me to
| password protect in FrontPage (as the creator said, "The FrontPage way!").
| Prior to this I had tried to use the hosting service's Control
Panel/utility
| only to have htaccess and FrontPage Extensions corrupted each time the
user
| names and passwords were added or deleted, or when FrontPage Extensions
had
| to be reinstalled.
|
| As I mentioned, password protection is working, but now I have the
conflict
| of the local and remote sites being one in the same.
|
| I'm feeling a little stupid, at this moment... so please help!
|
| Thanks,
|
| Patrick

 

[Guest]

Tom:

Thanks for the quick response.

Are you saying that because I published "live," per the procedure, that I
can no longer publish from FrontPage? In other words, am I going to have to
make all of my updates "live" on the remote site, and can no longer Publish
from FrontPage? Is there no way to "separate" the local from the remote and
still retain password protection -- in other words, revert back to publishing
from FrontPage and not directly on the remote site? The procedure that I
followed required that I publish "live" in order to create the pasword
protection -- administrative, user, etc.

Thanks,

Patrick

 

[Tom Willett]

How are you trying to open your local site?
--
===
Tom Willett
Microsoft MVP - FrontPage
---
FrontPage Support:
http://www.frontpagemvps.com/
===
| Tom:
|
| Thanks for the quick response.
|
| Are you saying that because I published "live," per the procedure, that I
| can no longer publish from FrontPage? In other words, am I going to have
to
| make all of my updates "live" on the remote site, and can no longer
Publish
| from FrontPage? Is there no way to "separate" the local from the remote
and
| still retain password protection -- in other words, revert back to
publishing
| from FrontPage and not directly on the remote site? The procedure that I
| followed required that I publish "live" in order to create the pasword
| protection -- administrative, user, etc.
|
| Thanks,
|
| Patrick
|
|
| "Tom Willett" wrote:
|
| > If you are actually making the changes on the live remote site, you
can't
| > publish. It's already there. You just save the page(s) you're working
on.
| > --
| > ===
| > Tom Willett
| > Microsoft MVP - FrontPage
| > ---
| > FrontPage Support:
| > http://www.frontpagemvps.com/
| > ===
| > | > | Hello Pros:
| > |
| > | Need your help.
| > |
| > | I use FrontPage 2003.
| > |
| > | Recently I published "live," per the instructions I was given, in
order to
| > | password protect my site -- two folders (sub-sites).
| > |
| > | Everything seemed to go smoothly until I attempted to make some
changes
| > and
| > | publish. I was greeted, "quite rudely," with a message that stated
that
| > both
| > | the local and remotes sites were the same, thus I could not publish,
nor
| > | could I "reverse" publish, remote to local.
| > |
| > | I have checked everywhere I could think of, but I could not find any
way
| > to
| > | correct this conflict.
| > |
| > | I'm sure it will be quite obvious to you, and you will wonder why I
| > couldn't
| > | see the solution, but I need your help. I've drawn a blank,
especially in
| > | that I was following someone else's procedure.
| > |
| > | For the record, consequetly, all of the subsequent changes/updates I
have
| > | made, to my site in FrontPage, are actually being made directly on the
| > remote
| > | site... and password protect does work. Btw, the procedure enabled me
to
| > | password protect in FrontPage (as the creator said, "The FrontPage
way!").
| > | Prior to this I had tried to use the hosting service's Control
| > Panel/utility
| > | only to have htaccess and FrontPage Extensions corrupted each time the
| > user
| > | names and passwords were added or deleted, or when FrontPage
Extensions
| > had
| > | to be reinstalled.
| > |
| > | As I mentioned, password protection is working, but now I have the
| > conflict
| > | of the local and remote sites being one in the same.
| > |
| > | I'm feeling a little stupid, at this moment... so please help!
| > |
| > | Thanks,
| > |
| > | Patrick
| >
| >
| >

 

[Guest]

Tom:

As I do for all of my sites... I either find a recently accessed site and
select it, or I Open Site. Neither way now allows me to publish from
FrontPage, I now get the message that the local and remote sites are the same.

When my computer crashed, several months ago, I was able to "reverse
publish" -- in order to get the current version that I had published back
into FrontPage -- it was not a password protected site. But, since I created
this password protected site, which required that I publish "live," I no
longer have a local site separate from the remote, according to FrontPage.
And, when I try to publish I can not get beyond the error message.

Thanks,

Patrick

 

[Ronx]

Open the website in FrontPage.
Click Remote Web Site tab below the folders pane.
Click Remote Site Properties
Select File System
In the "Remote Web Site location" space, type in (or browse to) a folder
on your PC.
Click OK
Publish Local to Remote
Here the "Local" site is the site on the server, the Remote site is the
site on your PC. The local site is ALWAYS the site you open first, the
Remote site is ALWAYS the site in the right column. The physical
locations of these sites makes no difference.

When you open the site on tour PC, it will become the Local site, since
it was opened first.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.

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

FrontPage Support: http://www.frontpagemvps.com/

 

[Guest]

Ronx:

I sincerely thank you, and appreciate receiving your "directions"... I'll be
following your instructions as soon as I can bring that system up.

Thanks again,

Patrick