Frontpage wants to save pages to local temp directory

[Steve D.]

Lately when I open a page on my website to update it, the path in the title
bar changes to a long temp directory path on my computer (a copy of the file,
ie FILE[1].htm), and when I try to save the revised file, it wants to save it
there, rather than on my site. Why? This is very frustrating. It forces me to
renavigate to and log in to the site to save it, and then it often gives me
the error message that it cannot save to a file name that is open. What
causes Frontpage to want to name it a temp file on my harddrive rather than
keeping the original website path and name?

Thanks.

 

[Steve D.]

One other thing... Why does it take Frontpage so long to save changes to a
page online? The site seems plenty fast, but when I click the Save button to
save changes, sometimes it saves immediately, but often I get an hourglass
for about 5 minutes or so before it saves the changes. During this time the
program is "locked" and I can't do anything. What is going on?

 

[Steve D.]

P.S. I'm using FP 2003 on Win XP

 

[Ronx]

Opening a page in FrontPage using "Edit in FrontPage" from IE is
unreliable. The page is often opened from the browser cache rather than
the web site, and the edited page will always be saved back to where it
was opened from.
You could make sure that your browser always checks the web site before
loading from the cache[1], but I don't know if this makes any
difference.

[1] (for IE7)
In IE, Tools->Internet Options - General Tab
Under Browsing History, Click Settings
Select the radio "Every time I visit the webpage

IE6 may use Temporary Internet Files instead of Browsing History.

 

[Ronx]

Could be because you have hundreds of files in the FrontPage temporary
folder - deleting these may speed things up.
Another possible problem is the server itself - it may be busy with
other websites or admin tasks (backup?) at the time you are saving the
page. Some hosts do overload their servers.

Saving a page to a FrontPage extended site requires at least 6 tasks:
1) Upload the page to a temporary file
2) Rebuild the page with included or shared border files that are on the
server, if these are used in the page.
3) change code for forms in the page that use FP extensions
4) rename the temporary file to its correct name
5) update the meta data in the _vti_cnf folder
6) update other meta data files, including the index for WAIS search if
used.

This is not as straight forward as a simple FTP upload/save.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.

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

One other thing... Why does it take Frontpage so long to save changes to a
page online? The site seems plenty fast, but when I click the Save button to
save changes, sometimes it saves immediately, but often I get an hourglass
for about 5 minutes or so before it saves the changes. During this time the
program is "locked" and I can't do anything. What is going on?
--
Steve

Lately when I open a page on my website to update it, the path in the title
bar changes to a long temp directory path on my computer (a copy of the file,
ie FILE[1].htm), and when I try to save the revised file, it wants to save it
there, rather than on my site. Why? This is very frustrating. It forces me to
renavigate to and log in to the site to save it, and then it often gives me
the error message that it cannot save to a file name that is open. What
causes Frontpage to want to name it a temp file on my harddrive rather than
keeping the original website path and name?

Thanks.

 

[Steve D.]

Ah... the cache, that makes sense. Thanks so much for the explanations!