Add pager option 'Reverse page order'

An excellent idea - should all the pager code offer this either as an option or standard?

Yes, someone thinking the same way I am thinking, with the reverse order the site automatically becomes a index. I remember when embaumsworld was popular, they we used to search out the content was looking between a 3 page spread of where we thought we saw it. without the reverse after a year the site is completely changed. (I wonder which is better for SEO, I think it sort of removes duplicate content to a degree, idk)

I think revers page order is good for SEO and for people to bookmark.
It would be greate if developers include this feature to core pager of Drupal.

If you want the core queue modified, then this hsould be filed against Drupal.

There is progress on this issue?
One of the solutions (6.x): http://drupal.ru/node/25387#comment-141042

sub

Subscribe - would be great for SEO, bookmarking, etc...

Subscribe.
I was hoping this feature will be in Drupal 7... but not :(

I'm using this code changes on my multisite drupal installation to make reversed pagination on all Drupal pagers:
http://toopro.org/drupal/seo-pagination-reversed

Sounds good, but I can't imagine how to do it. We have nodes 1-10 in page 1, node 11-20 in page 2...? So if there is 25 nodes, we display the first 10 nodes (16-25), in which page are we (for bookmark)?

Is there any CMS/forum that does it?

It was the question for me too.

I think filled pages don't need to be changed, but the first, not fully filled page, that don't have number (its address will be "/node") must get additional nodes from previous page to show 10 nodes.

There will be only one problem - user will read some nodes twice :(
But benefits are more important as for me.
Users just need to think about "/node" address not like this is a regular other pages in list, but like the list of last 10 nodes added.

Of course for implementing in Drupal core we have to try find better solution of this problem, but I can't remember right now sites with this type of pagination.

sub first, may add patch soon

Threads about this on d.o:

• Reverse Page Order?
• pager reverse order
• Reverse pager

Which pagers exactly does this issue affect? Taxonomy and 'Promoted to front page'?
Would each contrib module offering pagination have to implement this, too? Or is core offering some kind of API that contrib could use?

- Anyone could post some ref about the benefit.
- use cases
- and what will it look like..?
I took an example from gdo.
First Previous 5 [4] 3 2 1 Next Latest

Previous is linking to ?? Page 3 or 5.

- Anyone could post some ref about the benefit.
- use cases

@droplet: Let me try to explain it.

I think this feature request only makes sense for content sorted reverse chronological ("newest first"). The most prominent use-case would be any kind of news section/blog.

Let's say we have a blog with 27 entries, 10 entries per page (entry 1 is the oldest one):

Now the blogger publishes 11 more entries:

No entry (teaser) is on the same page anymore. The first entry was on page № 1, now it is on page № 2.

Consequence: all pager URLs are broken (well, the URL is still there, but with totally different content)

• all search engines have to re-index the content of all pages, every time the blogger posts some entries
• visitors (coming from search engines) expect different content (if the seach engine didn't yet re-index)
• all bookmarks are broken (Bob wants to read all blog posts, stops at page № 7, bookmarks it, comes back some days later, and … woosh, not where he stopped anymore)
• no chance to link to a certain page, if you want to discuss exactly that selection of entries ("look, my first ten entries")

With a reverse page order, you get:

And after 11 new entries:

= 3 more entries on page № 3 and a new page № 4. All old entries are still linked at the same page (and will be there forever, until you delete some entries, of course).

- and what will it look like..?
First Previous 5 [4] 3 2 1 Next Latest

Previous is linking to ?? Page 3 or 5.

In this example, "Previous" on page № 4 would link to page № 5.

I think __for (reverse) chronological sorted content__ it would make more sense to name the links "Newer" and "Older" (instead of "Previous" and "Next").
And it's a (much discussed) question if you want to go left (for LTR languages) for the newest or for the oldest content. There is no undisputed answer to this (I think that would better fit into an own issue, if there is need to discuss it).

@no2e If we have 27 entries then we display only 7 for the first page? If we have 21, then we display only 1?

@jcisio: Yes, I'd think so.
With ascending page order, the last page could be "incomplete".
With descending page order, the first page could be "incomplete".

I don't think is a big problem. It is this first page most users will encounter first, so they won't know at this point how many entries per page should be displayed usually.

Currently going through the end of the queue to see what could still be relevant for D10.

I'm also not seeing the use case for this one but does sound like it could be useful to some.

Will need an issue summary update.

A webcomic is a good use case for this. Usually, the front page of a webcomic site is the most recent page, and you read/ navigate "backwards" from there.

Problem/Motivation

Currently, pagination in Drupal follows the standard ascending order (1, 2, 3, …). When new nodes are added and the page limit is reached (e.g., 10 per page), older nodes shift to different pages, causing two issues:

User Experience: Users memorize page numbers, and when they return, content is no longer in the expected location.
SEO Concerns: Search engine bots (e.g., Googlebot) index pages based on their URLs. When content shifts, bots detect different content on the same URLs, leading to unnecessary reindexing, possible ranking penalties, and incorrect search results.

Steps to reproduce

• Create a view with a paginated list of nodes, ordered by descending creation time.
• Set the page limit to a fixed number (e.g., 10 per page).
• Observe the pagination pattern (1, 2, 3, …).
• Add new nodes and notice how older nodes shift to different pages, disrupting memorized URLs and positions.

Proposed resolution

• Implement an option in Drupal’s Views pagination to reverse the numbering.
• Instead of 1, 2, 3, ... use a descending pattern like 45, 44, 43, ... for a total of 45 pages.
• Ensure that when new nodes are added, older ones remain on the same page number.

Remaining tasks

• Identify the best method to implement reversed pagination.
• Modify Drupal Views or pagination logic to allow descending page numbers.
• Provide configuration options to enable/disable this feature.
• Test for compatibility with existing themes and modules.
• Ensure SEO benefits are achieved and document the improvements.

User interface changes

A new option in Views configuration to enable reversed pagination.

Introduced terminology

Reversed pagination: A pagination method where page numbers count down instead of up.

API changes

Potential modifications to pagination handling in Views.

Data model changes

No database schema changes are required.

Release notes snippet

Added an option in Views to enable reversed pagination, allowing page numbers to count down instead of up. This helps maintain content consistency for returning users and improves SEO by reducing unnecessary reindexing.