The last couple of days, threads and posts have not been acknowledged in Firefox as “read”; that is, I read a thread, leave/reload the forum, and the thread is still highlighted. When I click the “go to first new post” button, I go to the same post as the first time, a post I’ve already read.
Any idea what’s going on?
Same thing happens to me, and I am using IE7. I thought it may have been because I switch between Verizon DSL and Charter Cable, but now I wonder.
I’ve seen this too. Just chalked it up to some intermittent slowness in my system, which is unusual and unexpected for Comcast cable, usually it’s pretty fast but I’ve had some real slow-motion going on this week.
I don’t think it’s just here – I’ve seen this problem elsewhere as well.
Anyone else seeing system-wide problems like this anywhere else?
I got exactly the opposite problem-threads are already reset to “read” the instant I arrive here and go to read one.
So you’re taking all our page views, is that it? 
Okay, now this is weird. As far as I know we have changed nothing here so nothing should be happening.
I don’t know if this will help, but at GB we had a problem where the number of thread views wasn’t changing. vBulletin runs a bunch of regular processes, including one which updates the thread view tallies, but it had crashed because the threadview table was corrupted.
Once we repaired the table (On the Admin panel, it’s the Repair/Optimize option under the Maintenance tab, select the table(s) to repair and/or optimize and click continue, and then reran the process (Scheduled Task Manager under Scheduled Tasks) everything was fine. Took less than five minutes.
Give how close our vB versions are, you might give that a try.
On a possibly related note, my last visit for this site is marked as yesterday, even though I have logged out and back on since then. On the GB, the log-in info is correctly noted.
Sorry to bump, but the problem seems to have returned (in that the board seems to have an imperfect view of what “new/unread” posts are).
Try clearing your cache and cookies, and see if it still happens. If that doesn’t help, try using another browser and see if it still happens. That way you’ll know if it’s an issue with your specific browser or not. It’s updating fine for me in all browsers, so it’s unlikely (in this specific instance) to be a server specific issue.
Hmm. Cache and cookie clear didn’t help, but the problem did not replicate in Safari, so it looks like it’s something to do with Firefox (3.5.7 on Mac). Any ideas on fix/workaround?
ETA: Odd; seems that going directly to the last post (via that column in the general forum listing) marks the thread as read, as it should when I actually do that in-thread.
Try this:
Meaning of each value:
0 - Check for a new version of a page once per session (a session starts when the first application window opens and ends when the last application window closes).
1 - Check for a new version every time a page is loaded.
2 - Never check for a new version - always load the page from cache.
3- Check for a new version when the page is out of date. (Default)
If that doesn’t work, check your Firefox extensions. You might have to selectively uninstall extensions to see if any of them are conflicting.
Seems to work, thanks (in that threads are actually being marked as read now)! I wonder why this started happening; I hadn’t quit out of the Firefox application (or indeed, shut off my computer - just sleep) in over a week, but I don’t see how that would’ve done it.
Is there a reason why 3 is the default? Will it affect performance somehow?
Glad it worked. Not sure exactly why it’s happening with you, but usually a corrupted cache causes this.
3 is default because it is a compromise between performance and always refreshed pages. Most pages on the Internet don’t change substantially.
It will affect performance in that it will refresh every page every time, thus taking more time (and bandwidth) to load the page than it would have taken to load the same page from cache. Practically, the difference will be in milliseconds or at max a few seconds per page, depending on your connection speed. So the difference won’t be very noticeable. If you find that websites you visit are loading at about the same speed as before, you have nothing to be concerned about.
Your DNS server might have more of an impact on website loading speeds. I recommend Google DNS, and have found it to resolve websites consistently faster than the DNS servers of the default ISPs I use at various locations. To change your DNS server settings, read the instructions here:
Since I first registered months ago my ‘time last visited’ has always been curious. I haven’t paid much attention so I cannot describe it. It just doesn’t look correct most of the time.