You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
The Badge shows a file was edited 420 years ago
Is anyone else having issues with Badge, randomly showing "<user> last edited this file 420 years ago".
it seems to affect both mac and windows users and appears to be random- in that we can't ...
I know this issue sucks big time, and I hate being the bearer of bad news...but
https://help.dropbox.com/installs/badge-overview
The timing and exact functionality of these features may change, and Dropbox doesn't provide warranties on the performance of these features.
Jay
Dropbox Staff
Dropbox StaffHi martychaos, thanks for posting today!
This is more of an issue that can occur with Windows, where a modification date of a file can be changed to the year 1601.
Some research on this matter can be made after checking on the web regarding this date, and could possibly be a conflict with Windows/Unix systems on how they calculate time.
If the file is 'modified' on that date, then Dropbox would see it, and thus report it that way. It might be worth trying to edit the file quickly while on a Windows machine to see if this helps.
Keep me updated with any progress!
This is more of an issue that can occur with Windows, where a modification date of a file can be changed to the year 1601.
Some research on this matter can be made after checking on the web regarding this date, and could possibly be a conflict with Windows/Unix systems on how they calculate time.
If the file is 'modified' on that date, then Dropbox would see it, and thus report it that way. It might be worth trying to edit the file quickly while on a Windows machine to see if this helps.
Keep me updated with any progress!
I am having the same issue, where one of my user's file changes are being dated 420 years ago. Dropbox, please fix this issue!
Hi All,
still no fix, issue still appearing occasionally and as far as I know- no one is changing their file/folder dates to 1601.
I still can not find a replicable cause either.
Hey @dropboxsupport how about addressing this?
cheers
March 2023 and still not fixed. What is the deal? I find it hard to believe it's not a Dropbox issue.
DropBox;
That is COMPLETE AND TOTAL BS!!
and yes, I meant to yell at you;-)
In our shop we are running 3 dif versions of Windows & 3 of macOS.
Dropbox App fully updated on all machines and we still get "edited 421 years ago" on some files.
it's the same wrong edit date on a few files across ALL users and all computers.
One of the main reasons we use dropbox is because of the file version mgmt and the badge showing who and when a user edited a file.
That functionality is critical to our business ........all day long, every day.
If y'all cannot resolve this (clearly dropbox) error then I will have to seek another vendor's solution.
Which, I don't want to do as I like dropbox ............except for this unresolved bug
all of our 7 users use windows machines and we see there edits happening 420 years ago jay, stop with the runaround and get the issue resolved. there are zero other applications, programs or files that have this issue. dropbox is completely alone in this and has the issue outstanding for the entire 4 plus years we have been a customer
That is COMPLETE AND TOTAL BS!!
and yes, I meant to yell at you;-)
In our shop we are running 3 dif versions of Windows & 3 of macOS.
Dropbox App fully updated on all machines and we still get "edited 421 years ago" on some files.
it's the same wrong edit date on a few files across ALL users and all computers.
One of the main reasons we use dropbox is because of the file version mgmt and the badge showing who and when a user edited a file.
That functionality is critical to our business ........all day long, every day.
If y'all cannot resolve this (clearly dropbox) error then I will have to seek another vendor's solution.
Which, I don't want to do as I like dropbox ............except for this unresolved bug.
