Disqus showing incorrect timestamp on posts

134 views
Skip to first unread message

Ewan Fisher

unread,
Dec 4, 2013, 3:32:15 PM12/4/13
to disqu...@googlegroups.com
Hi there
I have recently integrated disqus into my bigcommerce store at proto-pic.co.uk
Ive noticed that the comments show up on the store as being posted a month ago etc, when they were only jusy posted within the last couple of hours.
The store is set to gmt timezone as is my disqus dashboard settings (im in uk).The comments show with the correct timestamp in the dashboard so it must be to do with the integration. Bigcommerce server is in houston with a cdn in london, if i believe correctly.
Any help would be appreciated
Regards
Ewan

Gabriel Fouasnon

unread,
Dec 4, 2013, 3:36:22 PM12/4/13
to disqu...@googlegroups.com
Can you send a link to a specific page where you see the problem?


Ewan

--
You received this message because you are subscribed to the Google Groups "Disqus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to disqus-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Ewan Fisher

unread,
Dec 9, 2013, 5:56:56 AM12/9/13
to disqu...@googlegroups.com
Sure thing:
 
The comment by Edward cate and the reply by roy show they were added a month ago - it was in fact less than two weeks ago.
 
regards
richard

Gabriel Fouasnon

unread,
Dec 9, 2013, 3:28:09 PM12/9/13
to disqu...@googlegroups.com
Hmm.

I looked up the comment by Edward Cate, and it shows the following timestamp:

  "createdAt":"2013-11-04T20:51:52",
If that timestamp is correct, then the application is correct to output "a month ago" for this comment.

I don't believe we've gotten any reports about our servers incorrectly time-stamping comments, but we'll keep an eye out.

I also posted a comment on the page you linked (a comment which I then deleted) and it showed a correct timestamp "a few seconds ago".

Are you still seeing this problem? Is it recurring or was it a one-time thing? 

Oh, one possibility that just occurred to me is that if your browser clock is off, then you'll get an incorrect relative timestamp. Because the display logic works like this:

current browser time - comment time -> transform into human readable timestring ("a few seconds ago", "one month ago", etc.)

Tell me, what happens when you enter the following code in your browser's console (the same browser where you see the bug):

var d = new Date();
console.log(d.toString(), d.toUTCString());

?

Best,
Gabriel - Engineer at Disqus


--
Reply all
Reply to author
Forward
0 new messages