I've noticed some strange things today

[Drewcifer]

In the Conquests forum all of the threads are out of order. Also on all of the forums it no longer tells us who else is browsing the forum. I assume this has something to do with the upgrade.

 

[Drewcifer]

Even though I just posted this thread there is another above it with a time one hour in the future. Have we discovered time travel?

 

[TedJackson]

From the front page:

Edit: Forum problem is fixed now. Also, the server time is now correct. However, because the server was 12 hours fast after the upgrade, the time stamps for posts made after the upgrade got messed up. It will take about 24 hours for us to get past all the messed up time stamps.


Ted

 

[Aggie]

This explains everything! I saw my post two pages back. I;m happy that it is sorted out.

I usually skip the front page. I did check it before I posted my remarks in Site Feedback, but I didn't realise the impact of it

 

[Stapel]

Current post are ok again. Some old posts still have a future time!

It is all worth the new server!!!!

 

[FredLC]

Oh... Than I see why some of the replies are ending up before previous messages in the same thread (it happened in both discussions I opened last night in th OT);

Oddily enough, one of that discussions ahds top do with temporal anomalies in a movie. Oh, the irony...

Anyway, it's very confusing to the reader. Is it possible for the MODs to fix that?

The threads are:

http://forums.civfanatics.com/showthread.php?s=&threadid=56124

and

http://forums.civfanatics.com/showthread.php?s=&threadid=56135

regards .

 

[LKendter]

Well the time is back to normal, but that post are fragged for the night!

I have no idea what was missed. I hope this is the end of it!

 

[Civanator]

the only explainable reason:
We have discovered time travel!

But this is kind of funny, seeing a post I made last night apear to be posted 3 hours in the future today

 

[Aggie]

OK, the time issue is explained.

But what the info about users browsing this forum. I really miss that

 

[Dell19]

Perhaps TF has still not gotten round to installing that addition to the forum or it failed to update with the forum so it had to be removed for awhile.

 

[Sultan Bhargash]

My post in OT at 1047 EST still came out before a much earlier post: wierd to see people answer my questions before I ask them in the weight loss thread.

 

[WillJ]

Originally posted by Aggie
But what the info about users browsing this forum. I really miss that

I think the "users browsing this forum" list was getting really messed up. Take a look at this thread (the second "oddity"). I wonder if it had to do with the time thing, but I can't figure out how it could have anything to do with that.

 

[MadScot]

WillJ

It could be time related as follows:

VBulletin might store your "latest log on" and "most recent log off" times - I bet it uses something like those for the "new posts since you were here last" thing.

So, it's really 1000UTC. But in CFC-land, everyone is at 1400UTC. So when the machine tries to work out who else is online, it finds out no-one - they will all be online *later* it seems. To a human that would be obvious evidence of a major screwup. To the code, it's just an answer. So it tells you no-one is online *now*.

Just a thought?

 

[WillJ]

Originally posted by MadScot
WillJ

It could be time related as follows:

VBulletin might store your "latest log on" and "most recent log off" times - I bet it uses something like those for the "new posts since you were here last" thing.

So, it's really 1000UTC. But in CFC-land, everyone is at 1400UTC. So when the machine tries to work out who else is online, it finds out no-one - they will all be online *later* it seems. To a human that would be obvious evidence of a major screwup. To the code, it's just an answer. So it tells you no-one is online *now*.

Just a thought?

But lot's of people were listed as online, not no one.

 

[MadScot]

Sorry

Maybe it compares to log off time - which is in the future - but doesnt check the log on time, also in the future?

Or, if the system clock is fast relative to the stored times, it's checking the log ons but not log offs?

Someone who knew something about the mechanism would be better qualified, I'm just guessing wildly