Publishing problems--changed files not publishing

[Mark]

In Frontpage 2002:
When publishing our web, some changed files are not being
published. It is set for "publish changed pages only,"
which is essential because I've got almost six gigs of pdf
files for public access, but I don't want to have to
publish all of them each time. We have two Frontpage
licenses, so only two of us publish the web, but other
users will make changes to the pdfs and save them to the
web folder on our LAN. If they create new pdfs (pdfs with
new names) those files publish, but changing a pdf file
but keeping the name, and those files don't publish. These
files are not set for "do not publish," and I have gone to
the "options," "publish" tab and tried both settings
(determine changes by file timestamp and determine changes
by comparing local and remote webs) and neither helps.

I can publish the file by highlighting it in the left pane
of the publish window and selecting "publish selected
files," or I can use a stand-alone ftp program to delete
the file from the web server, and frontpage will then
publish the changed file as a new file.

I'd like to be able to simply rely on Frontpage to
identify the new or changed files and upload them for me.
Is there something I'm missing? Thanks!

 

[Kevin Spencer]

If you make changes to a file thqat resides in a FrontPage web without using
FrontPage to first open the web and then open or export/import the file
to/from the web, FrontPage will have no way of knowing that the file was
changed.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

 

[Stefan B Rusynko]

Every time you reopen the FP web/site run a Tools Recalculate Hyperlinks for FP to attempt to find the stuff you may have changed
outside of FP

--




| If you make changes to a file thqat resides in a FrontPage web without using
| FrontPage to first open the web and then open or export/import the file
| to/from the web, FrontPage will have no way of knowing that the file was
| changed.
|
| --
| HTH,
| Kevin Spencer
| .Net Developer
| Microsoft MVP
| Big things are made up
| of lots of little things.
|
| | > In Frontpage 2002:
| > When publishing our web, some changed files are not being
| > published. It is set for "publish changed pages only,"
| > which is essential because I've got almost six gigs of pdf
| > files for public access, but I don't want to have to
| > publish all of them each time. We have two Frontpage
| > licenses, so only two of us publish the web, but other
| > users will make changes to the pdfs and save them to the
| > web folder on our LAN. If they create new pdfs (pdfs with
| > new names) those files publish, but changing a pdf file
| > but keeping the name, and those files don't publish. These
| > files are not set for "do not publish," and I have gone to
| > the "options," "publish" tab and tried both settings
| > (determine changes by file timestamp and determine changes
| > by comparing local and remote webs) and neither helps.
| >
| > I can publish the file by highlighting it in the left pane
| > of the publish window and selecting "publish selected
| > files," or I can use a stand-alone ftp program to delete
| > the file from the web server, and frontpage will then
| > publish the changed file as a new file.
| >
| > I'd like to be able to simply rely on Frontpage to
| > identify the new or changed files and upload them for me.
| > Is there something I'm missing? Thanks!
|
|

 

[Mark]

OK, just to be clear, the fact that the file, while it has
the same name, is of a different size and has a different
date, does not trigger frontpage to publish it? How does
it know to publish files with new names that are simply
copied into the local web folder?

mark

 

[Jim Buyens]

If the people who are changing the pdf files aren't saving
them via FrontPage, that's your problem. FrontPage doesn't
know the files have changed!

You could solve this by recalculating hyperlinks before
every Publish operation, but that's going to be a time-
consuming operation.

I would design this so that the 6 gigs of pdf files aren't
part of any FrontPage Web at all. For example, here are
two possible approaches:

o Put the pdf files on a different,
non-FrontPage-extended virtual server, and link to
them there.

o Put the pdf files in an ordinary disk folder, not
part of any http root. Then, write an ASP or ASP.NET
page that reads specified files from that location and
pushes them into the Response stream.

You don't explain how Web visitors find the file they
want, but with either approach above you could write some
ASP or ASP.NET code to read the pdf folder tree on the
server and display menu pages.

Or, you could write some maintenance pages that authorized
people would use to simultaneously upload pdf files and
record database information about them. Web visitors could
then search the database for documents of interest and
receive a menu of hits.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
|| Microsoft FrontPage Version 2002 Inside Out
|| Web Database Development Step by Step .NET Edition
|| Troubleshooting Microsoft FrontPage 2002
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Stefan B Rusynko]

Not if FP doesn't know you changed it
- see my post above

--




| OK, just to be clear, the fact that the file, while it has
| the same name, is of a different size and has a different
| date, does not trigger frontpage to publish it? How does
| it know to publish files with new names that are simply
| copied into the local web folder?
|
| mark
|
| >-----Original Message-----
| >If you make changes to a file thqat resides in a
| FrontPage web without using
| >FrontPage to first open the web and then open or
| export/import the file
| >to/from the web, FrontPage will have no way of knowing
| that the file was
| >changed.
| >
| >--
| >HTH,
| >Kevin Spencer
| >..Net Developer
| >Microsoft MVP
| >Big things are made up
| >of lots of little things.
| >
|

 

[Guest]

I also have this happen alot! Even with recalculate hyperlinks.

My first solution is to rename the page ie:index2.htm and publish it, then rename it back.

Second solution is to delete the original from the web side first, then republish changed page.

Graphics sometimes have the same problem because FP makes temp files. Rename, insert renamed graphic, save and name back.

http://designcadunleashed.com

 

[Mark]

I get what you're saying; my problem is that these are
files that are accessed by a script rather than a
hyperlink, so Frontpage never knows they are there.
Although, when I just dump a new file into one of the
folders on the local web, it does publish that file to the
web server; it just doesn't work when the file has been
changed (pages added or removed from a pdf) but has the
same file name.

I used to use a third party FTP app to upload these files,
but it does take an extra step and some file management to
identify the new files; I had been hoping that FP would
prevent my having to it.

Thanks for the information!

mark

 

[Stefan B Rusynko]

Doesn't matter how they are referenced (script or not) FP still manages all files based on File New or File Import (or drag and drop
which triggers File Import) thru the _vti_cnf files it creates for each file (and summarizes in the web cache file - *.web)

If you bypass that, by saving into the FP Web w/ FP closed, it will not recognize the file as being updated (or even there for a new
file)

Running Tools Recalculate Hyperlinks causes FP to relook at all files in the web and update the FP configuration files to reflect
the latest date/time stamps of all files in the site (as well as check/update all webbots)

The only thing different FP does w/ script referenced files is not update links to those files
(when you move, rename, delete them)

For non-html files (like media and pdf) that are updated often in-place, put them all in one folder & link to them from your pages,
then convert that folder to a subweb (never open it in FP) and FTP to just that folder

--




| I get what you're saying; my problem is that these are
| files that are accessed by a script rather than a
| hyperlink, so Frontpage never knows they are there.
| Although, when I just dump a new file into one of the
| folders on the local web, it does publish that file to the
| web server; it just doesn't work when the file has been
| changed (pages added or removed from a pdf) but has the
| same file name.
|
| I used to use a third party FTP app to upload these files,
| but it does take an extra step and some file management to
| identify the new files; I had been hoping that FP would
| prevent my having to it.
|
| Thanks for the information!
|
| mark