Originally posted by Illuvatar
My only concern is that this appears to be a known bug(as I've seen other posts re. this issue), so is this something that can be addressed in v3.0?
My only concern is that this appears to be a known bug(as I've seen other posts re. this issue), so is this something that can be addressed in v3.0?
"It's a limit of how the date() function works on certain systems. Breaks in Windows as well. Times less than Jan 1, 1970 will be negative relative to the epoch, and some OS's don't handle that. (I saw this once before on a *nix box, but I can't remember the specifics of the setup.)"
Comment