When there are no unread posts and I reply to a topic it, the main page will show no unread posts which is correct but the forum boards show my post a 'New' item, shouldn't this not show up as I just created it!?
Yay for SMF bugs.
That's behaviour we've inherited from SMF - since return-to-topic is the default (and is default even in the distribution), you never go to the message index, so it never clears that board as being having unread. SMF is exactly the same in that regard.
In fact the only behaviour we've really changed is that unread doesn't differentiate between 'since last session' and 'forever', meaning that you won't get things appearing and disappearing there.
That's behaviour we've inherited from SMF - since return-to-topic is the default (and is default even in the distribution), you never go to the message index, so it never clears that board as being having unread. SMF is exactly the same in that regard.
In fact the only behaviour we've really changed is that unread doesn't differentiate between 'since last session' and 'forever', meaning that you won't get things appearing and disappearing there.
nend
- We-Gen
-



- When is a theme, no longer what it was when installed?
- Posts: 163
I noticed that behavior on my SMF installation also. I was wondering about what was the cause. I haven't dug in there yet but any possible solutions?
It shouldn't be hard to fix. Just an extra query in Post2.php I'd say... :)
![]() | ...« I say wedge wedge (in the butt) » « Everyone knows rock attained perfection in 1974. It's a scientific fact. » (Homer Simpson) |
Yeah, I think I mentioned a couple of weeks ago another bug with it...
i.e. a sub-board was marked as read in the homepage, and as soon as I read one of the unread topics in it, it lost its 'unread' flag even though there were more unread topics in it.
i.e. a sub-board was marked as read in the homepage, and as soon as I read one of the unread topics in it, it lost its 'unread' flag even though there were more unread topics in it.
![]() | ...« I say wedge wedge (in the butt) » « Everyone knows rock attained perfection in 1974. It's a scientific fact. » (Homer Simpson) |
Yup. It's broken however you slice it, really. But none of the systems really has it completely right, because they always have to tread performance vs accuracy.
vBulletin for example considers all posts to be read in a post once they're past a certain age, for example.
vBulletin for example considers all posts to be read in a post once they're past a certain age, for example.
nend
- We-Gen
-



- When is a theme, no longer what it was when installed?
- Posts: 163
Can't you have both, you can do slow queries that return no information via JavaScript after the page has loaded. Would that be a good time to do clean up?
Can't you have both, you can do slow queries that return no information via JavaScript after the page has loaded. Would that be a good time to do clean up?
![]() | The way it's meant to be |
It might make a difference on nginx/PHP-FPM setups but for folks on Apache/PHP/mod-php, it makes no difference at all, doubly so when mod-gzip is enabled, since Apache will wait until PHP ends execution before returning to the user.
The only way around that is process forking and even I'm not crazy enough to go down that particular rabbit hole with Wedge. I've done it in other cases and it can work, but not for this case.
The only way around that is process forking and even I'm not crazy enough to go down that particular rabbit hole with Wedge. I've done it in other cases and it can work, but not for this case.
nend
- We-Gen
-



- When is a theme, no longer what it was when installed?
- Posts: 163
I was more like saying pass it on to JavaScript for a second request, not run it with the main page load. It should be transparent.
I was more like saying pass it on to JavaScript for a second request, not run it with the main page load. It should be transparent.
![]() | The way it's meant to be |
nend
- We-Gen
-



- When is a theme, no longer what it was when installed?
- Posts: 163
Ultimately that'll lead to even more load, as the queries for session authentication will have to be run twice plus the query to get the unread itself along with various other queries that are run.Quote from nend on June 8th, 2012, 07:51 PM I was more like saying pass it on to JavaScript for a second request, not run it with the main page load. It should be transparent.
I'm still not sure how best to deal with this particular little quagmire. I'm sure SMF's solution is not the best, but at the same time I'm not sure how best to fix it, since I'm not sure I'd want it to flag a given board as read if I've only replied to something very new.
Perhaps we should just do that, if your post is the newest in a given board, mark the board as read.
Perhaps we should just do that, if your post is the newest in a given board, mark the board as read.
nend
- We-Gen
-



- When is a theme, no longer what it was when installed?
- Posts: 163
I am debating on removing the new icon for boards. I can see appeal of leaving them too. :whistle:





