Make WordPress Core

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#46374 closed defect (bug) (invalid)

Admin panel custom post pagination showing same results

Reported by: speedwheel's profile speedwheel Owned by:
Milestone: Priority: normal
Severity: minor Version:
Component: General Keywords:
Focuses: administration Cc:


I have a custom post registered inside wordpress. There are in total 28 items inside, 20 items per page (default).

When I navigate to page 2, I still see arond 5-6 items that were on the first page, but in the same time I have some missing items, which I can see only if I choose to see at least 28 items on a single page.

I have the latest wordpress.

Here is a screenshot:

Attachments (2)

1.JPG (84.0 KB) - added by speedwheel 5 years ago.
2.JPG (75.4 KB) - added by speedwheel 5 years ago.
This is the second page

Download all attachments as: .zip

Change History (8)

5 years ago

5 years ago

This is the second page

#1 @mukesh27
5 years ago

  • Focuses accessibility removed
  • Keywords reporter-feedback added
  • Severity changed from normal to minor

Hi @speedwheel, Welcome to WordPress Trac! Thank you for your ticket.

As per your attached screenshot you have created two same name post 2 times that's why that post was displayed in second page.

For example in page 1 post Rebecca Lyn Dodd is created 51 mins ago and in page 2 post Rebecca Lyn Dodd is created 38 mins ago, Both the post created in different time so remove duplicate post then it will resolve above issue.

#2 @speedwheel
5 years ago

Hello @mukesh27.

Actually I had the second page opened for a while, but I refreshed the first page (that's why the different times), there are no duplicates.

But I found the problem. I imported these 28 posts using WP All Import, and looking at the database it seems that all those 28 posts have the same date (including seconds), which means that the default sort (by date) will not work, if I switch to 'sort by title', then it works fine.

I will just change the date manually in the database.

#3 @mukesh27
5 years ago

@speedwheel above issue is resolved or still need further investigation?

#4 @speedwheel
5 years ago

@mukesh27 It's fixed thanks.

#5 @mukesh27
5 years ago

  • Resolution set to invalid
  • Status changed from new to closed

Going to close this ticket.

#6 @desrosj
5 years ago

  • Keywords reporter-feedback removed
  • Milestone Awaiting Review deleted
Note: See TracTickets for help on using tickets.