WordPress.org

Make WordPress Core

Opened 11 years ago

Closed 10 years ago

#2972 closed enhancement (wontfix)

Reversed page numbering

Reported by: FireMotion Owned by:
Milestone: Priority: lowest
Severity: minor Version: 2.0
Component: General Keywords:
Focuses: Cc:

Description

Currently, the most recent page (in any of the archives -- dated, categorized) is page number 0. When clicking on Next Page, the url shows it being paged=1, thus page number 1. Going back even further, the page numbers increase.

However, when new posts are added, all the content in the pages shift with it.

In my opinion, it would be better if the oldest posts would be on page 1. This way, if new posts are added, consequently new pages are added. AND the content of the pages stay the same.

---

An example in the current situation:

  • There are 30 posts
  • Because of paging, they are spread over 3 pages.
  • The first post is on page 2.
  • The most recent post 30 is on page 0, post 21 is on page 0, post 20 on page 1
  • When creating a new post, post 31 and 30 are on page 0, page 21 shifts to page 1, page 20 is on page 1.
Posts 30 to 21Posts 20 to 11Posts 10 to 1
Page 0Page 1Page 2

New post added:

Post 31Posts 30 to 21Posts 20 to 11Posts 10 to 1
Page 0Page 1Page 2Page 3

---

Example in the ideal situation:

  • There are 30 posts
  • Because of paging, they are spread over 3 pages.
  • The first post is on page 1.
  • The most recent post 30 is on page 3, post 21 is on page 3, post 20 on page 2
  • When creating a new post, post 31 is on page 4, post 30, 21 and 20 stay on their own pages.
Posts 30 to 21Posts 20 to 11Posts 10 to 1
Page 3Page 2Page 1

New post added:

Post 31Posts 30 to 21Posts 20 to 11Posts 10 to 1
Page 4Page 3Page 2Page 1

---

Pros:

  • This results in better navigation.
  • People can more easily bookmark pages.
  • Search engines can more easily index the pages.

Cons:

  • The newest page might only contain 1 to x posts.
  • A bit more complex code or SQL statements.

Change History (3)

#1 @foolswisdom
11 years ago

  • Milestone changed from 2.5 to 2.2

#2 @foolswisdom
11 years ago

  • Milestone changed from 2.2 to 2.4

#3 @Nazgul
10 years ago

  • Milestone 2.4 (future) deleted
  • Resolution set to wontfix
  • Status changed from new to closed

No traction for almost a year, so closing as wontfix.

Feel free to reopen it if you have additional info/patches/comments/...

Note: See TracTickets for help on using tickets.