https://www.drupal.org/files/issues/pager-issue.png

We are using Drupal 7.x (with Views v7.x-3.11)
It helps to paginate the list.

But I noticed that it uses array index (0...n) instead actual page number (1...n) for pagination. For example I was having long list of contacts with 27 pages pagination. When I hover over the hover text on 'Last' link in pagination is 'Go to last page' but in the browser status bar it displays '?page=26' which is correct as per array index, but it should be '?page=27' a user point of view. Similarly if you hover on say '3' in pagination it says 'Go to page 3', but in status bar it displays '?page=2'.

In an address bar, it displays the same ie. '?page=26'. Some of users tried to directly hit '?page=27' as they seen '27' link in pagination, but getting nothing.

Can we fix this issue? Can we use actual paginate numbers instead array index?

CommentFileSizeAuthor
pager-issue.png15.88 KBamolnw2778
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

amolnw2778’s picture

amolnw2778 CreditAttribution: amolnw2778 commented
Category: Support request » Bug report
amolnw2778’s picture

amolnw2778 CreditAttribution: amolnw2778 as a volunteer and at Tieto commented
amolnw2778’s picture

amolnw2778 CreditAttribution: amolnw2778 as a volunteer and at Tieto commented
Issue summary: View changes
Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

I'm very interested in this too, but as seen in the issue below, unless the change is made in core there probably won't be any in views.

https://www.drupal.org/node/1818040

doublejosh’s picture

doublejosh CreditAttribution: doublejosh as a volunteer commented

Pretty small issue to stop you from using the entirety of the Views ecosystem. It's been the case to use the index value for the param for many years, expect the fix to take a bit more work than you might expect.

Also, there's little chance this would be changed in D7. Too many modules are likely to depend on this.