Pagination, reverse page order

Created on 13 May 2007, almost 18 years ago
Updated 26 June 2023, almost 2 years ago

Hi

As you know page numbers is like 1 2 3 4 ...
And when 10 nodes added and if the page limit is 10 then the page numbers stay as they are and the nodes move from one page to the other.

to avoid this i tried to create the page numbers like : 45 44 43 42 .... instead of 1 2 3 4 .... if we have 45 pages. This way when new nodes are added the ones on the last page will have still the same page number. Of course i am talking about a view with tons of nodes and where the nodes are ordered by descending creation time.

There are mainly 2 reasons why i try to reverse the page numbers:

1- users memorise the page numbers, and after some time when they come back, all the nodes are moved to other pages since lots of nodes are added.

2- google bot and other bots memorises the page numbers, and when it comes back it sees that all pages with the same url have different pages, and thinks that it should reindex reindex reindex.... keep indexing. and when displaying result to its' users bots always point to a wrong page. And this i believe drops the page rank of the site.

I wonder if anyone can help me to reverse the page numbers.

thank you
arda

โœจ Feature request
Status

Active

Version

9.5

Component
Viewsย  โ†’

Last updated about 11 hours ago

Created by

๐Ÿ‡น๐Ÿ‡ทTurkey arda

Live updates comments and jobs are added and updated live.
  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States smustgrave

    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.

  • ๐Ÿ‡ณ๐Ÿ‡ฑNetherlands johnv
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States ixlr8

    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.

  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia anjalibarad

    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.

Production build 0.71.5 2024