Forums Forums Search & Filter Pro Duplicated item in pagination

Viewing 8 posts - 1 through 8 (of 8 total)
  • Anonymous
    #50295

    We have a section of a website that lists out items from a custom post type, has 12 items/page, and displays pagination using WP-PageNavi: http://dev.bopdesign.com/perrknight/resources/downloads/

    The second item, “Bureau Monitoring Brochure,” displays on every page in the pagination, though the post is not duplicated in the back-end.

    Do you know why this could be happening?

    Thanks!

    Trevor
    #50320

    The results give a total of 26 items, of which one item appears 3 times then? If you actually go to the back end, how many posts should there be in these results?

    Anonymous
    #50366

    Looking at this a little more carefully, it seems that all of the posts are being duplicated except for one. It’s displaying unique posts on page one. Page two has one new post and then displays the rest of the posts in the reverse order of the first page.

    Here’s a breakdown of what it seems to be doing:
    Page One: posts 1-12
    Page Two: post 13, then post 1, then posts 12-3
    Page Three: posts 2 and 1

    The interesting thing is, when we change the number of posts per page so it displays all of the posts at once, the repetition goes away.

    Anonymous
    #50374

    I forgot to mention that we also tried disabling the WP-PageNavi plugin. It didn’t fix the problem.

    Trevor
    #50418

    Are you using the ‘random’ order sort? Or any form of sorting?

    Anonymous
    #50490

    Hi Trevor,
    The only sort setting is by ‘menu order’.

    Thanks,
    John

    Trevor
    #50547

    Are you up to try a pre-release copy of the next version (2.2.0) to see if this fixes it? If so, send me a private reply with your email address.

    Anonymous
    #50613

    Hi Trevor,

    We were able to fix the problem by doing the following:

    a. Switching the CPT to “hierarchical”
    b. Switching the sorting to “menu order”

    I’m not sure what would cause the bug we had previously, but this work-around seems to be working just fine for now.

    Thanks!

Viewing 8 posts - 1 through 8 (of 8 total)