Issue information
-
#035588
-
Fixed
-
3.3.0 Beta 1
-
3.3.0
-
1 - Low
Issue Confirmations
-
Yes (0)No (0)
1
330A6
With a fresh install, the default "Welcome" topic has a date of 1st Jan 1970 showing.
Strangely, this *only* appears in forum view. Topic view and board index view are fine.
I could not see anything immediately amiss with the timestamps in the topics / posts tables (any new topics created are fine) apart from the default topic has no post key in the post table, not sure if that's normal or not given its inserted during the install.
With a fresh install, the default "Welcome" topic has a date of 1st Jan 1970 showing.
Strangely, this *only* appears in forum view. Topic view and board index view are fine.
I could not see anything immediately amiss with the timestamps in the topics / posts tables (any new topics created are fine) apart from the default topic has no post key in the post table, not sure if that's normal or not given its inserted during the install.
I'll retest, I note that's A4 (did not do it on that version that I'd noticed)
Although it says Alpha 4, it's actually the latest from SVN.
OK
I've just done two fresh installs, one A4 and one A6. The A6 still did it:
A4, all OK:
A6, still has it:
EDIT... Will see what next build does then I guess. , not a big issue anyways.
I've just done two fresh installs, one A4 and one A6. The A6 still did it:
A4, all OK:
A6, still has it:
EDIT... Will see what next build does then I guess.
, not a big issue anyways.
Andy: that would be a problem with your server installation, we don't populate the date field manually but use the mysql function "UNIX_TIMESTAMP()".
teraßyte, on 31 January 2012 - 01:01 PM, said:
Andy: that would be a problem with your server installation, we don't populate the date field manually but use the mysql function "UNIX_TIMESTAMP()".
I was going to (try) to remember to check at the next build to see if it was still present or not.
Nope, it's been like that since IPB 3.0 I think...
Its still present, although I'll have to await to see if anyone else can reproduce it, not really much of an issue regardless No problem.
No problem.
The latest build still does this, to me at least. 
Have to await to see if it happens to anyone else.
Have to await to see if it happens to anyone else.
Not sure if 3.3.0 Beta 4 counts, but it is still present for me atleast
Yes it was the latest Beta4 build.
As its not just me then ( thankfully ) I'll change this back to unfiled so a dev can have a quick look at this issue again, although its not a big issue anyway.
As its not just me then ( thankfully
) I'll change this back to unfiled so a dev can have a quick look at this issue again, although its not a big issue anyway.
I fixed this in passing while looking for something else.
0 user(s) are reading this issue
0 members, 0 guests, 0 anonymous users
