I agree that it's nice to see what is new. I don't read all posts either.

The reason I like the new system a lot better is that when I'm done reading what I want I can mark the forum as read by clicking on " Quick Links" and then "Mark Forums Read". I can mark a sub forum as read if I don't want to mark the complete forum as read if say I only had time to look at a sub forum or two. The next time I look at the forum I can see what is new.

With the old system it would sometimes timeout and mark the forum as read in the middle of trying to read it. Then you don't know what is new without looking at the time stamps if you remember the time last time you looked. With the old system I would not look at the forum unless I thought I had time to look at everything I wanted to see. I also wouldn't post sometimes as I knew it would time out while I typed.

Exactly the same reason for me. The old way was, to me, a system admin in a previous life, absolutely not efficient. Too much time wasted looking at wrongly marked read threads for posts I might have missed. This does NOT happen anymore.

In addition to a search for unread posts, some other forums I use have a way to memorize a query for new messages since last visit. If we had both it would seem the best of both worlds. Users could look for either all unread or just new since last visit - which is essentially what the old configuration did once they all flipped to "read".

This board has a lot of message activity. While I primarily read and post in just a few forums I like to skim the active thread topics regardless of forum. The short timeout before they were automatically marked read meant that I would miss things if I took too long, got interrupted, etc.

+1

I like the new system. I have lost count of the number of times I would spend enough time in a forum that it ended up marking everything read in the forums I had not yet looked at. Especially if a thread had link that I would follow. If I followed and read several of the links bikeforums would log me off and bingo! Everything is read, even the stuff that hasn't been read.

Same here. Don't use the feature. Don't use several of them...I use new posts and scan a few forums, trim subscripitions when I'm done with the thread or it's closed, even moved to P&R.


I may be a P&R superstar and I never use it, just by default of the thread getting moved there.

I like the new system MUCH better, until recently, that is.

Starting a few weeks ago, when I click on Forum Tools and Mark This Forum Read, nothing happens. Now, my unread thread lists grows and grows. What is really wierd is that sometimes reading a thread clears it from the unread list, but if I Mark This Forum Read, it can reset a huge list back to unread. WTF? Is anyone else having this problem?

I have logged out and logged in again, I cleared my browser cache, I have cleared my cookies, I shut off all my browser extensions, and I even restarted my computer and did the whole thing over. But no luck.

Interestingly, though - if I use Chrome, I get this unexplainable behaviour. If I logout and use Safari, it seems to work (at least until I login with Chrome again). So it seems like Chrome is the culprit. Anyone have any ideas? I am at a total loss here.

I just tested this on chrome browser and was able to successfully mark forums as read using the link provided under "quick links"

Perhaps check for any privacy setting or incognito mode that may be causing this.

That's actually a different tool than I was referring to, but I got the same behaviour. So it is not something caused by the Chrome browser in particular, just my installation of it.

Good suggestion. I did some digging and noticed that Chrome was warning me that cookies were being blocked, even though I explicitly white-listed the site to allow cookies. I also noted some other strange behaviour regarding javascript (allowed it, but I suspect it wasn't functioning). On a hunch, I loaded the site securely (by adding https:// to the URL), and now it seems to behave normally. I have no idea why, but at least it is working again. So thanks for the tips.