HomeUser Control Panel (unavailable in archive)ForumsTutorialsArt GalleryResourcesMaps

date problem

01-19-2006, 03:10 AM#1
yoda_24
Someone else has probably noticed this but I didn't see anything about it so... here's a little problem with the dates. And this isn't the most recent thread so it shouldn't be listed here. Many times I've seen threads that were not the most recent listed as the most recent.

I wasn't even born in 1969 and neither was this site... or the internet in todays form...

Zoom (requires log in)
01-19-2006, 03:15 AM#2
Tiki
Its a php problem consisting of the timestamp table, they dono how there echoing it.
01-19-2006, 05:20 AM#3
yoda_24
I know.
01-19-2006, 09:35 AM#4
olofmoleman
Quote:
Originally Posted by yoda_24
Someone else has probably noticed this but I didn't see anything about it so... here's a little problem with the dates. And this isn't the most recent thread so it shouldn't be listed here. Many times I've seen threads that were not the most recent listed as the most recent.

I wasn't even born in 1969 and neither was this site... or the internet in todays form...

Zoom (requires log in)
It's all one big conspiracy, they only want you to think it's the year 2006
Attached Images
File type: jpgmessed up.jpg (57.4 KB)
01-19-2006, 10:24 AM#5
iNfraNe
Also, try refreshing the gallery. It will show other pictures each refresh :) (that is the same problem ofcourse)

I do wonder how you got 1969 tho, since timestamps start at 1jan1970. Negative timestamp ? :)
01-19-2006, 10:29 AM#6
Whitehorn
Well, its a day before, so -1 I guess :)
01-19-2006, 12:10 PM#7
iNfraNe
-86400 u mean ;)
(or that would be 0:00am, not 7pm)
01-19-2006, 12:54 PM#8
Jacek
I don't have problems with getting a date :)
01-19-2006, 02:20 PM#9
Tiki
Mines always Dec 31 1969 when I do it wrong.
01-19-2006, 02:59 PM#10
Vexorian
It happens when the thread was not moved.

So it looks allright for aproved resources, but screwed for submit a resource and gallery images.

I did some changes the other day to consider the last move date over the thread creation date. Although I used JOIN for that, weird stuff. I will check what's wrong with it

And no, it is not a timestamp problem, It is because the returned dateline is null

edit: things fixed, thread closed