ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Weird Bug with the 21st Post

    Announcements
    3
    7
    4.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • thanksajdotcomT
      thanksajdotcom
      last edited by

      I've noticed that whenever I click on the newest unread post in the unread section, as I'm going through, if it's on the 21st post, it goes to a blank page. However, if you change that number at the top in the URL from 21 to 20, it goes to the 20th post on page 1, and you can see post 21 right there below it. I don't know why it goes to a blank page. It's as if it thinks you should be on page 2 but you're not supposed to. Not sure if @scottalanmiller should submit a bug report to NodeBB, but that's an ongoing issue I've found.

      Thanks,
      A.J.

      1 Reply Last reply Reply Quote -1
      • scottalanmillerS
        scottalanmiller
        last edited by

        Yeah, that's a bug in the pagination. Manually editing the RESTful API is the only solution for the moment. Not sure if this one has been reported to NodeBB Devs yet but it is a consistent issue that I have seen.

        1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller
          last edited by

          https://community.nodebb.org/topic/2392/pagination-issue-with-blank-page

          1 Reply Last reply Reply Quote 0
          • thanksajdotcomT
            thanksajdotcom
            last edited by

            From the thread, the admins are saying we're unique.

            1 Reply Last reply Reply Quote -1
            • scottalanmillerS
              scottalanmiller
              last edited by

              That's not exactly what it said. It only said that the issue is not happening on the development branch and that no one looked at the production branch. So it really tells us extremely little.

              1 Reply Last reply Reply Quote 0
              • Reid CooperR
                Reid Cooper
                last edited by

                Could it be related to the template? As I understand it, template issues are what is causing the problem with the tags displaying improperly too.

                1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller
                  last edited by

                  That's reasonable. It could be.

                  1 Reply Last reply Reply Quote 0
                  • 1 / 1
                  • First post
                    Last post