I have unmatched files after synchronization. Why?

[JHolmes900]

After I published, I had half of my files identified as unmatched. I used
help and it told me the files needed to be synchronized. I performed
synchronization, but the files are still identified as unmatched.

 

[Mike Condron]

I have also experienced this. I made it stop by changing from "Determine
changes by comparing..." to "Use source file timestamps ..." in the "Remote
Web Site Properties" dialog, on the "Publishing" tab. There seems to be a
problem with whatever FP does to "compare" the source and destination sites.

 

[rdmac]

I am having the same problem. I also switched to use "file timestamp.." but
now the files and web pages show as "changed" every time I sync the two sites
they continue to show changed. They should show as "unchanged" after the
synchronization. I got an MS error which using FP the other day and that is
when this problem started. Can anyone else out there help with this problem ?
Thanks....

 

[Mike Condron]

Yes, I think I spoke too soon. I discovered the same "changed" effect soon
after I posted my previous reply. Now I'm stumped.

To make matters worse, when you update the website, sometimes it seems the
file dates change to today's date, so it looks like your remote site is more
current than your local site. This makes the "Use source file timestamps..."
option less useful than I thought. This too, however, seems inconsistent;
some files change, others don't.

I think there's just something basically wrong with how FP does the
comparisons. At first I thought maybe the HTML optimizations were causing
this because the page on the remote site isn't the same as the page on the
local site, but I'm getting this same problem with binary files like JPG
images, files that have identical data and identical timestamps.