G
Guest
how doi delect my old site from my web hosting site to publish a new less
usage on my site
usage on my site
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
X
xfile
Hi,
If I understood correctly, you wish to delete the old site hosted by an ISP
and publish a new site?
If so, you may not be able to delete the site, per se, - because many ISPs
will not allow you to add or remove sites (check with your ISP) but you can
delete all contents in the site.
There are two approaches to do that:
(1) Faster way by using FTP clients: Access the site with a FTP program
(such as CuteFTP), download all files and folders from the remote site to a
local folder for backup, and after that, delete everything in it. You can
then use the similar way to upload new files and folders to the remote site,
and then use FP to open the site and do the check if everything works fine.
(2) More appropriate way by using FP and FTP: Create a local site using FP,
and using FP publish all contents from the remote to the local site - this
will ensure the state of the local site is closely resemble to the remote
site. Use FTP client or FP to open the remote site and delete everything in
it - FTP is faster in many cases. Use FP again for publish new contents
from the local site (which is not the one you store the old contents from
the remote site) to the remote site.
Not sure if this is what you're asking for. Hope this helps.
If I understood correctly, you wish to delete the old site hosted by an ISP
and publish a new site?
If so, you may not be able to delete the site, per se, - because many ISPs
will not allow you to add or remove sites (check with your ISP) but you can
delete all contents in the site.
There are two approaches to do that:
(1) Faster way by using FTP clients: Access the site with a FTP program
(such as CuteFTP), download all files and folders from the remote site to a
local folder for backup, and after that, delete everything in it. You can
then use the similar way to upload new files and folders to the remote site,
and then use FP to open the site and do the check if everything works fine.
(2) More appropriate way by using FP and FTP: Create a local site using FP,
and using FP publish all contents from the remote to the local site - this
will ensure the state of the local site is closely resemble to the remote
site. Use FTP client or FP to open the remote site and delete everything in
it - FTP is faster in many cases. Use FP again for publish new contents
from the local site (which is not the one you store the old contents from
the remote site) to the remote site.
Not sure if this is what you're asking for. Hope this helps.
S
Steve Easton
Does the server have FrontPage extensions installed??
If so, open the "server" site in FrontPage and delete everything but the _private folder and the
images folder.
Then open the images folder and delete its contents, and then do the same for the _private folder.
close the remote site, open your local site and click File > Publish Web.
--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
If so, open the "server" site in FrontPage and delete everything but the _private folder and the
images folder.
Then open the images folder and delete its contents, and then do the same for the _private folder.
close the remote site, open your local site and click File > Publish Web.
--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
S
Steve Easton
Best way if the server has FrontPage extensions installed. Open the remote site in FrontPage and
delete the files.
--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
delete the files.
--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
T
Thomas A. Rowe
If you want to maintain the old content, you would need to publish it either back to your local PC
or to a subweb / subsite under the current site. You will then need to delete the old content in the
root web directly from within FP as indicated.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
or to a subweb / subsite under the current site. You will then need to delete the old content in the
root web directly from within FP as indicated.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
X
xfile
Hi,
Thanks for that and I will remember it as one of the approaches but I am not
sure if that is the "best way".
In any case, my suggestions were focusing on "backing up the existing data"
before doing the actual delete since many users including myself would
eventually find out the old date were not totally useless.
But many thanks for your suggestions as well.
Thanks for that and I will remember it as one of the approaches but I am not
sure if that is the "best way".
In any case, my suggestions were focusing on "backing up the existing data"
before doing the actual delete since many users including myself would
eventually find out the old date were not totally useless.
But many thanks for your suggestions as well.
T
Thomas A. Rowe
It is, if the FP extensions are installed on the remote server and you don't want to corrupt them
and you plan to continue to use FP to manage your web content, otherwise you can use any method you
want.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
and you plan to continue to use FP to manage your web content, otherwise you can use any method you
want.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
X
xfile
Hi,
As said, using FP is only one way but not necessary the only or the best way
for deleting contents.
As said, using FP is only one way but not necessary the only or the best way
for deleting contents.
X
xfile
Agree, but all of those conditions are self-assumed and not given by OP,
right?
I rest my case.
right?
I rest my case.
T
Thomas A. Rowe
Steve's reply does say, if the FP extensions are installed....
I did make a assumption with my reply initial reply that site has the FP extensions.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
I did make a assumption with my reply initial reply that site has the FP extensions.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
X
xfile
Besides, please read my original post under the second approach, I already
concurred using FP to open and delete contents after publishing to a local
site is one way.
I only mentioned, using FTP to delete files (after publishing back to the
local) might be faster and that applies only to the "delete" part of the
work.
concurred using FP to open and delete contents after publishing to a local
site is one way.
I only mentioned, using FTP to delete files (after publishing back to the
local) might be faster and that applies only to the "delete" part of the
work.
T
Thomas A. Rowe
If the remote server has the FP extensions, you do not want to use FTP to delete or any general to
manage any content.
The reason is that if you delete files and folders that have special use or permissions,
republishing or publish a new site from your local machine, will not replace or restore those
permissions on the live/remote server.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
manage any content.
The reason is that if you delete files and folders that have special use or permissions,
republishing or publish a new site from your local machine, will not replace or restore those
permissions on the live/remote server.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
X
xfile
And I already thanked Steve for that and humbly explained my focus which was
not incorrect in any ways.
No one but MVP can provide suggestions or can be correct?
not incorrect in any ways.
No one but MVP can provide suggestions or can be correct?
T
Thomas A. Rowe
My responses have nothing to do with being a MVP, I am a MVP because of my willingness to help FP
users.
My responses are based mostly on my experience with using FP since 1997, and working on 90+ web
design/development projects, all hosted on servers running the FP extensions, and participating in
this forum during the same period, have read over 122,000 post and replying to most with helpful
solutions to issue that users have.
There are many ways to do things, however some ways will always prevent problems from developing
later, other ways may create problems for users at some point, so I prefer to recommend solutions
that over time have proven to be the best overall solution (at least in my opinion).
Your approach of publish down a copy of the site first via FP is good, however your suggestion of
using a FTP application (because it is faster) to delete the content from the server will lead to
problems for the user, if they delete ALL of the content, which would include the extensions related
to their site, which can not be replaced by publish a local web back to the live/remote server, as
for one they will not longer be able to connect to the server via FP' http mode.
The user will have to contact the web host to re-install the extensions, unless they have Control
Panel access, and that may no even work. Also when content is managed via FTP or other applications
outside of FP, the FP extensions are not aware of any changes made to the site content, which can
and often does lead to problems.
If the live/remote server doesn't have the extensions, the user will not be able to publish down a
copy of the site via FP anyway, so they will have to use a FTP application to copy the content, and
if the site was developed with Themes, Shared Borders and/or FP Navigation component, the user will
have to re-apply the theme/shared borders and re-build the site's navigation structure on this local
copy of the site
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
users.
My responses are based mostly on my experience with using FP since 1997, and working on 90+ web
design/development projects, all hosted on servers running the FP extensions, and participating in
this forum during the same period, have read over 122,000 post and replying to most with helpful
solutions to issue that users have.
There are many ways to do things, however some ways will always prevent problems from developing
later, other ways may create problems for users at some point, so I prefer to recommend solutions
that over time have proven to be the best overall solution (at least in my opinion).
Your approach of publish down a copy of the site first via FP is good, however your suggestion of
using a FTP application (because it is faster) to delete the content from the server will lead to
problems for the user, if they delete ALL of the content, which would include the extensions related
to their site, which can not be replaced by publish a local web back to the live/remote server, as
for one they will not longer be able to connect to the server via FP' http mode.
The user will have to contact the web host to re-install the extensions, unless they have Control
Panel access, and that may no even work. Also when content is managed via FTP or other applications
outside of FP, the FP extensions are not aware of any changes made to the site content, which can
and often does lead to problems.
If the live/remote server doesn't have the extensions, the user will not be able to publish down a
copy of the site via FP anyway, so they will have to use a FTP application to copy the content, and
if the site was developed with Themes, Shared Borders and/or FP Navigation component, the user will
have to re-apply the theme/shared borders and re-build the site's navigation structure on this local
copy of the site
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.