http://www.perlmonks.org?node_id=414180

I just visited the Monastery Gates for the first time in a while and I noticed that the number of replies is incorrect. I checked several of the nodes on the front page, and all reply counts were off.

For example, MS SQL problem shows 9 replies on The Monastery Gates, but I only count 6. 2 of these six are second level replies.

Update: Just did a very quick check on SOPW, Discussions and Meditations and those counts look good.

Update: Looks like it has something to do with the "Show count of all replies" option at user settings

  • Comment on Wrong number of replies on Monastery Gates

Replies are listed 'Best First'.
Re: Wrong number of replies on Monastery Gates
by simonm (Vicar) on Dec 12, 2004 at 01:37 UTC
    In my browser, the front page shows "4 replies" for that node. Did you just mis-read it, or are you really getting a different count?
      No, I didn't misread it. I checked several nodes and I'm really getting a different count. It looks like a glitch counting nested replies.

      If you want to see it, go to User Settings and check "Show count of all replies". (I just unchecked it and went to the front page and now it's correct - "4 replies".)

        I noticed that one a while back but eventually worked out (or guessed as I didn't have confirmation) that it was indeed just counting the direct replies to each post and not the replies to those aforementioned replies.

        I guess it makes more sense that way as it's reflecting the actual number of "new" points / replies made to a post rather than just the following chat / debate ;)

        These days I tend to go straight to "newest nodes" when I log in anyhow as I find it easier to follow.

        --- Jay

        All code is untested unless otherwise stated.
        All opinions expressed are my own and are intended as guidance, not gospel; please treat what I say as such and as Abigail said Think for yourself.
        If in doubt ask.

        It's showing direct replies, not replies to replies, and "it's not a bug, it's a feature!". A feature of questionable value but probably DB performance related?