Speakeasy Forum timestamp in discussions

23 posts in
this discussion
ALL have the SAME timestamp NOVEMBER 7, 2018 1:00 AM PST

In the "could you give up X" discussion ALL the posts have a timestamp of NOVEMBER 1, 2018 12:24 PM PDT

PS...I just checked and see the same problem with posts in this forum also...ALL posts in a thread have the same time/date stamp.

Post was last edited on November 7, 2018 6:55 PM PST

Discussion is locked
Reply to: Speakeasy Forum timestamp in discussions
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: Speakeasy Forum timestamp in discussions
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
- Collapse -
Thank you JP for reporting this...

Looks like all threads are having the same symptoms.

Will report it to our team.

Thanks again!

- Collapse -
Thanks Lee

I don't know when this started..any chance the time change on the weekend Saturday night(lose an hour) triggered this?

- Collapse -
I wonder if

this is part of the "little bug " that's been causing Bob__B's troubles with e-mail updates Confused
I'm sure Lee's team is Hot on it's trail. Cool

- Collapse -
This is unrelated to the Tracked discussion bug.

I really wished it were that easy. But it's not Cry

- Collapse -
Hi Dig, All threads were affected.

But it is fixed now. Happy

- Collapse -
(NT) Groovy !
- Collapse -
(NT) Thanks Lee....time stamps are working properly now
- Collapse -
Yay! Sorry about that everyone..

It was an oops! A bad merge of code. Anyways back to business as usual.


CNET Forums

Forum Info