If you have a thread that's permenently marked unread,
1. Make a post in it
2. View the last page - This will clear out the post read but not fix the issue entirely, as it'll still think the second post is the latest post.
3. Open the thread again by clicking on the thread title (i.e. go the the #latest), view the last page fo the thread AGAIN.
4. Hope it works.
+12
Options
Inquisitor772 x Penny Arcade Fight Club ChampionA fixed point in space and timeRegistered Userregular
If you have a thread that's permenently marked unread,
1. Make a post in it
2. View the last page - This will clear out the post read but not fix the issue entirely, as it'll still think the second post is the latest post.
3. Open the thread again by clicking on the thread title (i.e. go the the #latest), view the last page fo the thread AGAIN.
4. Hope it works.
Update.... for me, simply making a post worked. The first time was on mobile. Then I checked the thread again from my work laptop. The post count was back up! But then I made another post, and the problem seems to have gone away again.
So, I don't know if that helps anyone.... but it seems like I had to apply the "fix" on every device I check the forums on? I'll find out more when I get home this evening and check the thread from my surface pro.
0
Options
El SkidThe frozen white northRegistered Userregular
Yeah, I was having that issue with the job thread too.
Making a post set it to being no new posts, though the first time I clicked on the thread name it took me back to the first page.
Going to the last page and going back and clicking on the thread name again seems to have fixed it? Bizarre...
Yeah, I was having that issue with the job thread too.
Making a post set it to being no new posts, though the first time I clicked on the thread name it took me back to the first page.
Going to the last page and going back and clicking on the thread name again seems to have fixed it? Bizarre...
Just did it with the new coronavirus thread.
Posting seemed to reset it to never having been initially viewed, at which point having to hit the last page to mark it read is normal behavior.
Is there something like a 'viewed' property for threads separate from latest read? I wonder if the request to initially set {viewed:true} is getting lost, but {latest:1} is still being set; which causes the observed shenanigans of latest not updating, and it doesn't try to update the viewed property again until you actually post in it.
Yeah, I was having that issue with the job thread too.
Making a post set it to being no new posts, though the first time I clicked on the thread name it took me back to the first page.
Going to the last page and going back and clicking on the thread name again seems to have fixed it? Bizarre...
Just did it with the new coronavirus thread.
Posting seemed to reset it to never having been initially viewed, at which point having to hit the last page to mark it read is normal behavior.
Is there something like a 'viewed' property for threads separate from latest read? I wonder if the request to initially set {viewed:true} is getting lost, but {latest:1} is still being set; which causes the observed shenanigans of latest not updating, and it doesn't try to update the viewed property again until you actually post in it.
Yeah, I was having that issue with the job thread too.
Making a post set it to being no new posts, though the first time I clicked on the thread name it took me back to the first page.
Going to the last page and going back and clicking on the thread name again seems to have fixed it? Bizarre...
Just did it with the new coronavirus thread.
Posting seemed to reset it to never having been initially viewed, at which point having to hit the last page to mark it read is normal behavior.
Is there something like a 'viewed' property for threads separate from latest read? I wonder if the request to initially set {viewed:true} is getting lost, but {latest:1} is still being set; which causes the observed shenanigans of latest not updating, and it doesn't try to update the viewed property again until you actually post in it.
Happened to me too.
Yeah other threads are working fine, but the new corona one will not flag as having been read and keeps going to the 2nd post.
+2
Options
NEO|PhyteThey follow the stars, bound together.Strands in a braid till the end.Registered Userregular
Looks like Vanilla finally got to the ticket you put in? unread threads appear to be behaving correctly again.
It was that somehow, from within the derelict-horror, they had learned a way to see inside an ugly, broken thing... And take away its pain.
Warframe/Steam: NFyt
All of the new Corona threads in D&D are still doing this for me. This will be especially frustrating since I won't have anything to post in some to do the "fix".
Assuming you mean the "threads won't update last-read post" bug that people were talking about recently, and not the title where "unread threads show as having 1 new post," I'm still having this. Not in all threads, but some, such as the General Coronavirus thread that was mentioned a couple posts above.
Doesn't matter whether I'm on desktop or mobile. Desktop is Chrome Version 81.0.4044.138 (Official Build) (64-bit). Mobile is Chrome 83.0.4103.88. Just for fun, I booted up Firefox to try (version 72.0.2 (64-bit)). Same thing.
Firefox here too (77.0.1 64 bit). Any new thread doesn't update last-read until I use the fix posted earlier (post in that thread, then read it again).
0
Options
Dhalphirdon't you open that trapdooryou're a fool if you dareRegistered Userregular
Having the issue on Brave, Version 1.9.80 Chromium: 81.0.4044.138 (Official Build) (64-bit)
Not sure if this will help, but for example... The new Police Brutality thread updates properly for me without me posting in it. The Covid discussion thread does not, even if I click through and read to the end or whatever, it always takes me to the second post in the thread as the "newest." This thread also doesn't update the count of new posts, it really just can't tell that I've read past the first post in the thread. I could post in that thread to fix it, though...
But maybe there's something behind-the-scenes that would help to compare what my account sees of these threads or not? Maybe!
Not sure if this will help, but for example... The new Police Brutality thread updates properly for me without me posting in it. The Covid discussion thread does not, even if I click through and read to the end or whatever, it always takes me to the second post in the thread as the "newest." This thread also doesn't update the count of new posts, it really just can't tell that I've read past the first post in the thread. I could post in that thread to fix it, though...
But maybe there's something behind-the-scenes that would help to compare what my account sees of these threads or not? Maybe!
Does it relate to your having bookmarked it when it was still on the first page (or first read it?) New police thread was on page 2 before I opened it, no issue.
Not sure if this will help, but for example... The new Police Brutality thread updates properly for me without me posting in it. The Covid discussion thread does not, even if I click through and read to the end or whatever, it always takes me to the second post in the thread as the "newest." This thread also doesn't update the count of new posts, it really just can't tell that I've read past the first post in the thread. I could post in that thread to fix it, though...
But maybe there's something behind-the-scenes that would help to compare what my account sees of these threads or not? Maybe!
Does it relate to your having bookmarked it when it was still on the first page (or first read it?) New police thread was on page 2 before I opened it, no issue.
I opened and bookmarked the Police thread on the first page. The other was too long ago, I don't remember
If you have a thread that's permenently marked unread,
1. Make a post in it
2. View the last page - This will clear out the post read but not fix the issue entirely, as it'll still think the second post is the latest post.
3. Open the thread again by clicking on the thread title (i.e. go the the #latest), view the last page fo the thread AGAIN.
4. Hope it works.
Yay that fixed it.
The bug happens when you bookmark a thread with unread posts. Only bookmark threads after you opened them from threadlist.
If you have a thread that's permenently marked unread,
1. Make a post in it
2. View the last page - This will clear out the post read but not fix the issue entirely, as it'll still think the second post is the latest post.
3. Open the thread again by clicking on the thread title (i.e. go the the #latest), view the last page fo the thread AGAIN.
4. Hope it works.
Yay that fixed it.
The bug happens when you bookmark a thread with unread posts. Only bookmark threads after you opened them from threadlist.
Neat, if that works I don't have to scour my brain for a post more substantial than "blue dot" for a thread I'm really only following, not contributing to.
If you have a thread that's permenently marked unread,
1. Make a post in it
2. View the last page - This will clear out the post read but not fix the issue entirely, as it'll still think the second post is the latest post.
3. Open the thread again by clicking on the thread title (i.e. go the the #latest), view the last page fo the thread AGAIN.
4. Hope it works.
Yay that fixed it.
The bug happens when you bookmark a thread with unread posts. Only bookmark threads after you opened them from threadlist.
Neat, if that works I don't have to scour my brain for a post more substantial than "blue dot" for a thread I'm really only following, not contributing to.
FWIW, I just tried this with the new police brutality thread in D&D. I click into the thread from the forum, read each page, and click back out to the forum. Thread still shows 93 unread and when I click back in it drops me into the first page still (I haven't bookmarked it yet).
Using Chrome (Version 84.0.4147.105 (Official Build) (64-bit)) on Windows 10 Pro.
If you have a thread that's permenently marked unread,
1. Make a post in it
2. View the last page - This will clear out the post read but not fix the issue entirely, as it'll still think the second post is the latest post.
3. Open the thread again by clicking on the thread title (i.e. go the the #latest), view the last page fo the thread AGAIN.
4. Hope it works.
Yay that fixed it.
The bug happens when you bookmark a thread with unread posts. Only bookmark threads after you opened them from threadlist.
Neat, if that works I don't have to scour my brain for a post more substantial than "blue dot" for a thread I'm really only following, not contributing to.
FWIW, I just tried this with the new police brutality thread in D&D. I click into the thread from the forum, read each page, and click back out to the forum. Thread still shows 93 unread and when I click back in it drops me into the first page still (I haven't bookmarked it yet).
Using Chrome (Version 84.0.4147.105 (Official Build) (64-bit)) on Windows 10 Pro.
Hmm weird. It's definitely worked every time for me so far, on mobile chrome.
I don't think I've ever had this problem on a thread I haven't bookmarked.
Bullhead, are you sure you hadn't bookmarked that thread previously? If you ever bookmarked it with the bug (even if you unbookmarked later), the bug will persist.
I don't think I've ever had this problem on a thread I haven't bookmarked.
Bullhead, are you sure you hadn't bookmarked that thread previously? If you ever bookmarked it with the bug (even if you unbookmarked later), the bug will persist.
I had, and I suspected that might be the case. Sucks I have to wait for a new thread to fix it, it's nearly impossible to keep up with that thread otherwise.
0
Options
Inquisitor772 x Penny Arcade Fight Club ChampionA fixed point in space and timeRegistered Userregular
I don't think I've ever had this problem on a thread I haven't bookmarked.
Bullhead, are you sure you hadn't bookmarked that thread previously? If you ever bookmarked it with the bug (even if you unbookmarked later), the bug will persist.
I had, and I suspected that might be the case. Sucks I have to wait for a new thread to fix it, it's nearly impossible to keep up with that thread otherwise.
Remove the bookmark, post in the thread, then enable the bookmark again. That's fixed it for me every time it's popped up, hopefully it will work for you.
I don't think I've ever had this problem on a thread I haven't bookmarked.
Bullhead, are you sure you hadn't bookmarked that thread previously? If you ever bookmarked it with the bug (even if you unbookmarked later), the bug will persist.
I had, and I suspected that might be the case. Sucks I have to wait for a new thread to fix it, it's nearly impossible to keep up with that thread otherwise.
Remove the bookmark, post in the thread, then enable the bookmark again. That's fixed it for me every time it's popped up, hopefully it will work for you.
Posting always fixes it, but I can't say I always have something to contribute and i hate cluttering them with a simple "Maek post to fix bug" post.
Something I noticed today. I had checked a thread , got to end. Backed out and was showing a new post but there wasn't one.
But the second to last post had an edit that wasn't there a few seconds before.
Are edits maybe what's showing as new?
I know whenever I edit a post in a thread, if there were any posts after mine, the forum 'forgets' that I already viewed those and flags the thread as having that many new posts again.
This bug, btw, seems fixed for me. Specifically, I'm referring to the one where if you bookmark a thread before reading to the end of the thread, the "Unread Posts" will never be updated until/unless you post in the thread. I'm not sure if a Vanilla bug was ever filed, but if other people can confirm, that bug could probably be closed.
(To verify this: I bookmarked a new thread, went to the end, and it marked the thread as no new posts. I also went to the end of a thread which had 100% had this problem in the past, and it is now marked as read.)
Same here. Mentioned it in the "D&D ... missing?" thread a few days ago, as I noticed it being gone like a few seconds before D&D disappeared. No idea if it was actually related, and maybe I should've posted it in this thread earlier then, too.
Anyway:
Just before conking out, it looked like the unread posts bug was fixed. (At least, one thread I had bookmarked suffering from that bug suddenly only had 18 new posts, instead of the ~1600 it listed before.)
Did some very minor testing, and I can no longer reproduce this bug. (That's the "Bookmark a thread before reading it, now 'last seen post' is stuck on the first page of the thread until you post in said thread."-bug) Maybe a coincidence, but uh, I'm glad it's gone either way.
So yes, can confirm that it's gone on my end as well.
Posts
Steam profile.
Getting started with BATTLETECH: Part 1 / Part 2
Try posting in it.
If you have a thread that's permenently marked unread,
1. Make a post in it
2. View the last page - This will clear out the post read but not fix the issue entirely, as it'll still think the second post is the latest post.
3. Open the thread again by clicking on the thread title (i.e. go the the #latest), view the last page fo the thread AGAIN.
4. Hope it works.
This fixed it for me as well.
Thanks to the fixers!
Steam profile.
Getting started with BATTLETECH: Part 1 / Part 2
So, I don't know if that helps anyone.... but it seems like I had to apply the "fix" on every device I check the forums on? I'll find out more when I get home this evening and check the thread from my surface pro.
Making a post set it to being no new posts, though the first time I clicked on the thread name it took me back to the first page.
Going to the last page and going back and clicking on the thread name again seems to have fixed it? Bizarre...
Just did it with the new coronavirus thread.
Posting seemed to reset it to never having been initially viewed, at which point having to hit the last page to mark it read is normal behavior.
Is there something like a 'viewed' property for threads separate from latest read? I wonder if the request to initially set {viewed:true} is getting lost, but {latest:1} is still being set; which causes the observed shenanigans of latest not updating, and it doesn't try to update the viewed property again until you actually post in it.
Happened to me too.
Yeah other threads are working fine, but the new corona one will not flag as having been read and keeps going to the 2nd post.
Warframe/Steam: NFyt
Still ongoing, the new general corona thread won't stay read
Doesn't matter whether I'm on desktop or mobile. Desktop is Chrome Version 81.0.4044.138 (Official Build) (64-bit). Mobile is Chrome 83.0.4103.88. Just for fun, I booted up Firefox to try (version 72.0.2 (64-bit)). Same thing.
3DS Friend Code: 3110-5393-4113
Steam profile
But maybe there's something behind-the-scenes that would help to compare what my account sees of these threads or not? Maybe!
3DS Friend Code: 3110-5393-4113
Steam profile
Does it relate to your having bookmarked it when it was still on the first page (or first read it?) New police thread was on page 2 before I opened it, no issue.
I opened and bookmarked the Police thread on the first page. The other was too long ago, I don't remember
3DS Friend Code: 3110-5393-4113
Steam profile
Bookmarked from forum index, opened, hit last page: Bugged
Opened, bookmarked, paged through: Fine
Opened, bookmarked, hit last page: Fine
Opened, hit back to forum link, bookmarked from index: Fine
Threads with less than 2 pages:
Opened WOW thread (2 replies), bookmarked, all posts read: awaiting new post
Opened Mashups thread (30-somthing replies), did not bookmark: Awaiting new post
3DS Friend Code: 3110-5393-4113
Steam profile
Neat, if that works I don't have to scour my brain for a post more substantial than "blue dot" for a thread I'm really only following, not contributing to.
FWIW, I just tried this with the new police brutality thread in D&D. I click into the thread from the forum, read each page, and click back out to the forum. Thread still shows 93 unread and when I click back in it drops me into the first page still (I haven't bookmarked it yet).
Using Chrome (Version 84.0.4147.105 (Official Build) (64-bit)) on Windows 10 Pro.
Hmm weird. It's definitely worked every time for me so far, on mobile chrome.
Bullhead, are you sure you hadn't bookmarked that thread previously? If you ever bookmarked it with the bug (even if you unbookmarked later), the bug will persist.
3DS Friend Code: 3110-5393-4113
Steam profile
I had, and I suspected that might be the case. Sucks I have to wait for a new thread to fix it, it's nearly impossible to keep up with that thread otherwise.
Remove the bookmark, post in the thread, then enable the bookmark again. That's fixed it for me every time it's popped up, hopefully it will work for you.
Posting always fixes it, but I can't say I always have something to contribute and i hate cluttering them with a simple "Maek post to fix bug" post.
But the second to last post had an edit that wasn't there a few seconds before.
Are edits maybe what's showing as new?
I know whenever I edit a post in a thread, if there were any posts after mine, the forum 'forgets' that I already viewed those and flags the thread as having that many new posts again.
(To verify this: I bookmarked a new thread, went to the end, and it marked the thread as no new posts. I also went to the end of a thread which had 100% had this problem in the past, and it is now marked as read.)
3DS Friend Code: 3110-5393-4113
Steam profile
Anyway:
So yes, can confirm that it's gone on my end as well.