I'm using BC 2.0 (build 167) to synch my website (via FTP) to my local PC. When I copy a file that has a date/time stamp of "1/1/2004 3:30:26 pm" to the web site the resulting file has a date/time stamp of "1/1/2003 3:30:00 pm." I don't mind losing the 26 seconds, but why am I losing an entire year?! When I connect to the web site using FTP in Windows Explorer the date modified shows as "1/1/2004 3:30 PM" so the implication is that the issue is with BC. (I know, I don't believe it either!)
Date is off by one year
Collapse
X
-
Re: Date is off by one year
Okay, this is getting even stranger. I just installed the 2.1 beta (build 211). Now the dates on the FTP server are exactly ONE DAY later than they should be. For example, SmartFTP shows a file having a date/time stamp of "12/5/2003 2:52 PM" which matches the date/time stamp on my local PC. But BC shows it as "12/6/2003 2:52 PM." Help!Comment
-
Re: Date is off by one year
I have the same problem. 2.0.3 (build 183)
Comparing local to remote via FTP. Yesterday, dates were off by one year. Today, all files older than 6 months (times show as 12 am) are fine. Files with actual timestamps are off by exactly one day. Remote shows one day later than local.
This is true on several sites hosted by different providers in different time zones.
All dates/times show correctly in my FTP client, FTP Voyager.
I have updates and synchronizations due on all these sites today. Please help.Comment
Comment