Forum software upgrade

[sswilson]

Just in case anybody else is looking for a solution to the post count issue. Logging out and logging back in cleared it for me.

It doesn't however appear to display a post after you've made it. IE 9.

[Nathan_P]

Well it hasn't for me, I'll log out again tonight and try again tomorrow and feed back to the admin's

[Grandpa_01]

I just tried it and it worked for me I now have 0 new post where I did have 237 new post.

[k1wi]

Logging out and back in sorts it for me: 300+ new posts back down to zero.

[bollix47]

I too logged out and back in earlier today and yes, it did reset the count back to zero but it climbs back up quickly. I've done the same more than a couple of times and the count always climbs up again. It's as if the read ones are not timing out and not dropping off.

[Dark Pulse]

Definitely can confirm that while logging out will clear it, posts will resume accumulating again from there.

[Jesse_V]

Definitely can confirm that while logging out will clear it, posts will resume accumulating again from there.

It's getting redundant for me to say this, but I too have confirmed that logging out and logging back in will reset it.

It wasn't flawless before this upgrade, (I don't think there should ever be 0 new posts) but it was much better than what it is currently doing. IMO, if a thread hasn't received a comment within four days of me last looking at it, it shouldn't be considered "new". If I still need it after that, I'm happy to look under "View your posts" or search for it directly.

[uncle_fungus]

Yep, this is definitely a bug, but unfortunately I won't be able to look at fixing it until Sunday at the earliest.

[Jesse_V]

Yep, this is definitely a bug, but unfortunately I won't be able to look at fixing it until Sunday at the earliest.

Hey that's no problem, no one's faulting you. Thanks for all that you do for us.

EDIT: here's another bug: it says "View new posts (77)" but I count 18 threads on the page.

[rhavern]

Not related to software upgrade, but related to changes at same time.

For consistency... •• Other: • Tools • WIKI •• Stanford time: 2012-08-09 14:21:21 •• ... if there is room.

Wasn't the Stanford time on a line of its own previously? Now, depending on the size of my browser window, it wraps around when the time appears and I get everything pushed down a line. When it was on its own line this didn't happen. Kind of annoying when you've started to read or are about to click and the page jumps.

Minor, but vaguely annoying.

Regards

[7im]

Yep, this is definitely a bug, but unfortunately I won't be able to look at fixing it until Sunday at the earliest.

Hey that's no problem, no one's faulting you. Thanks for all that you do for us.

EDIT: here's another bug: it says "View new posts (77)" but I count 18 threads on the page.

While I agree with ther being a problem, note that threads is not posts.There could be 4 new post in 17 of those threads, and 9 new posts in the last one. But since we only see one or two new "unread" posts, it doesn't match up lke u said.

[P5-133XL]

Actually counting the new posts are unlikely to match the view new posts list. There are multiple non-public forums (like the moderators forum). Posts in those forums show up in the new post count but unless you are a member of one of the hidden forums you won't be able to see them.

[bruce]

Jesse_V's problem is, as 7im says, the difference between the number of new posts and the number of threads that have new post(s) in them.

p5-133XL: Unless it has changed in the new version, the post count covers only posts in threads/forums that are visible tp the person doing the counting.

[uncle_fungus]

Little update here: I know what the problem is (last visit time is not being tracked correctly) but I don't as yet know how to fix it. The only work around so far is to actually log off rather than just close your browser window.

[bruce]

Logging out of the forum works, as noted. So does manually clicking "Mark forums read" The earlier version had a timeout which logged you off after a period of inactivity. You adjusted that timeout a couple of times, but it still changed your status to logged off overnight.