FP Not Changing Changed File's Properties?

[jim evans]

I have an .EXE file I update every few days. FrontPage still shows
the properties from an earlier version. Specifically the Date & Time.
The creation and modified dates are not the same but both are wrong
and from an earlier version.

After a publish (upload) FP reflects the same wrong date as the date
of the file on the server.

Why is this?

jim

 

[Ronx]

If you use File->Import (or Drag form Windows Explorer into the open
FrontPage web) to bring the updated .exe file into the website, the web
meta data will be updated. The timestamp shown in FrontPage is taken from
the meta data, not from the directory structure.
When you publish, the meta data on the server is updated, including the
timestamp from the local web meta data. If you publish "Changed Pages
Only" it is possible that the .exe is not uploaded at all, since the meta
data is still referring to a previous version.

Saving the updated file, or copying with Windows Explorer, into the web
folder does not update the meta data, hence FP does not "know" the file has
changed. Running Tools->Recalculate Hyperlinks may correct this.

 

[jim evans]

If you use File->Import (or Drag form Windows Explorer into the open
FrontPage web) to bring the updated .exe file into the website, the web
meta data will be updated. The timestamp shown in FrontPage is taken from
the meta data, not from the directory structure.
When you publish, the meta data on the server is updated, including the
timestamp from the local web meta data. If you publish "Changed Pages
Only" it is possible that the .exe is not uploaded at all, since the meta
data is still referring to a previous version.

Saving the updated file, or copying with Windows Explorer, into the web
folder does not update the meta data, hence FP does not "know" the file has
changed. Running Tools->Recalculate Hyperlinks may correct this.

Thanks for your reply.

If I understand you, FP does not check/update file properties of files
included in webs when it starts? That seems odd, but kay sera.

jim

 

[Mark Fitzpatrick]

Jim,
It only checks when it is told to, ie: when a file is imported
through FrontPage or some action such as a Recalculate Hyperlinks. This
keeps FP from performing long actions when the user doesn't want it to.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage

 

[Guest]

I'm having a similar problem, did a search before posting and found this.
Here's my question: we are updating documents in Word, saving them as an
Acrobat file and overwriting files in our website that already have
hyperlinks. I believe we are doing it the same way every time, but for some
reason, FrontPage will see some of the updated files and not others. I opened
"Publish Site" and checked the date on one that kept showing the "old"
version and, sure enough, it was hanging onto the old date. So, I
double-clicked to open it and it showed the updated version.

I ended up selecting it in the publishing window and then "published
selected files from local to remote site." That worked, but I'm trying to
avoid having to do all these extra procedures. Does anyone know why some
files seem to update just fine while others don't? I read the first
explanation in this posting, but still don't understand what's happening.
Sorry.

Anne W.

 

[Steve Easton]

Make sure you "always" import the updated files into FrontPage, or copy and paste them into FrontPage in folder view.
Otherwise FrontPage has no way of detecting the change.


--
Steve Easton
Microsoft MVP FrontPage
FP Cleaner
http://www.95isalive.com/fixes/fpclean.htm
Hit Me FP
http://www.95isalive.com/fixes/HitMeFP.htm