Post count wrong causing issues with navigation and notifications

  • NodeBB 1.9.2.

    Basically a couple of related issues which have started happening all of a sudden:

    1. Post count is incorrect. Example (this thread actually has about 598 posts):


    1. (Following on from previous issue) Clicking the "jump to last post" navigation button goes to post 400, not post 598

    2. Jumping / scrolling to the bottom of the thread causes additional posts to finally start loading beyond post 400, via infinite scroll. They load pretty quickly and eventually you can reach the end of the thread, but this obviously isn't expected behaviour

    3. The same thing happens when notifications are clicked, i.e. if someone posts a new comment in this thread, I get a notification but clicking it takes me to post 400, not their actual recent post:


    It's as if some cache or index is not being updated.

    Tried rebuilding/restarting with no success. No errors in the logs. Checked "Cache" under Advanced and "Group Cache" was full at one point (Length of 40000). I don't know what this means because there seems to be zero documentation about this.

  • Additionally, pagination doesn't seem to work at all any more, i.e. I cannot switch from infinite scroll to pagination.

    The option activates but the scrolling behaviour hasn't actually changed.

  • Anyone else ever experienced this or have any insights?

  • NodeBB Admin

    Looks like for whatever reason the postcount is out of sync, you can fix it with a mongodb query and see if the issue is resolved.

    Run this in mongo sell replacing the <tid> and <postcount> with the actual values.

    db.objects.update({_key: "topic:<tid>", {$set: {"postcount": <postcount>}}});

  • @baris Thanks, I'll give this a try but am using Redis. Any idea what the command should be for that?

  • GNU/Linux Admin

    @btc hset topic:<tid> postcount <postcount>

    But of course, replace <tid> and <postcount> as necessary.

Suggested Topics

  • 3
  • 4
  • 3
  • 6
  • 31
| | | |