LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   LQ Suggestions & Feedback (https://www.linuxquestions.org/questions/lq-suggestions-and-feedback-7/)
-   -   Some posts remain marked unread and have mismatched time stamps (https://www.linuxquestions.org/questions/lq-suggestions-and-feedback-7/some-posts-remain-marked-unread-and-have-mismatched-time-stamps-909645/)

SecretCode 10-23-2011 05:54 AM

Some posts remain marked unread and have mismatched time stamps
 
Something is wrong and I don't know what nor whether it can be fixed. But let me describe what I see ...

The majority of threads get correctly marked as read when you read them. So, as long as there are no new posts, I tend to rely on these features.

But some threads seem to get stuck (until you log off and mark all threads as read, or mark all threads in the given forum as read). They stay in bold and the "new post" button remains there - and always seems to take you to the first post in the thread.

What I've noticed - I'm not sure if it applies to all - is that these threads display a different (more recent) time in the list of threads than they do in the thread view. For example:
gedit save dialog defaults to 'Recently Used' is one of these stuck threads, for me. In the thread list it shows Last post: Today 08:44 but the post itself shows as Yesterday, 16:00 with no evidence of an edit.
HOWTO setup different system language and keyboard layout? also is 'stuck' and has a timestamp mismatch.

Some threads where the last post has been edited also seem to get stuck.

I wonder if this indicates something that the experts at vbulletin.com could use to identify the issue?

---------- Post added 2011-10-23 at 12:54 ----------

As a test - I'm going to edit this post.

Edit: to see if it gets stuck.

jeremy 10-23-2011 12:50 PM

The timestamp difference you're seeing is a result of the 0 reply auto-bump. We'll handle this more cleanly after the next code update.

--jeremy

SecretCode 10-23-2011 01:49 PM

Aha. I didn't know there was a 0-reply autobump, but it sounds good.

How far off is the code update likely to be? It's to vB 4 I assume, as running at AQ? If it's soon, I guess the problem of threads sticking in unread state should wait for it.

thanks
Joe

Michael Uplawski 11-06-2016 04:21 AM

Quote:

Originally Posted by SecretCode (Post 4505954)
How far off is the code update likely to be?

Erm... thank you. Found this thread, understand the issue.

“A bit far off” is my contribution. 06 november 2016. ;) Persists.


All times are GMT -5. The time now is 06:11 PM.