Results pager shows too many pages [#1518336]

The search results pager behaves as if their are 9+ pages of results, even if there are only a couple pages. Once you get to the last page of results, the pager displays correctly.

Other pagers on my site are behaving correctly.

Comment	File	Size	Author
	Screen Shot 2012-04-06 at 2.37.53 PM.png	15.88 KB	eusonic
	Screen Shot 2012-04-06 at 2.36.20 PM.png	17.29 KB	eusonic

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

mpgeek CreditAttribution: mpgeek commented 6 April 2012 at 21:52

Status:

Active

» Postponed (maintainer needs more info)

This is a known issue with public vs. access-controlled content, i believe. Have a look here:
http://groups.google.com/group/Google-Search-Appliance-Help/browse_threa...

I've been trying to figure out a workaround for the module, but the only thing i can think of is instead of performing another search query on paging (fake paging) we could just query for the first X number of records, then use a cache table and have the paging be "real" and local. I just haven't had time to work that out. Have a look in theme_google_appliance_pager (in google_appliance.theme.inc)... the comments there explain further.

If there are ideas, we are listening...

Comment #2

eusonic CreditAttribution: eusonic commented 6 April 2012 at 22:38

The comments in the code say "Device configuration can help." What configuration settings will help make the results count more reliable? We didn't set up the GSA (I don't think we even have access to it) so I'm not familiar with its configuration options.

Thanks
-Cameron

Comment #3

mpgeek CreditAttribution: mpgeek commented 6 April 2012 at 22:50

The thread on google groups makes it sound like if there were access control configured for the crawler on all possible places the crawl could end up, you would end up with a more accurate results count, i.e. the "estimate" would be closer to exact. That would require admin access to the GSA device itself, obviously.

That brings us back to the idea of pulling 1000 real, accessible results, then caching them and using the drupal pager the way it was intended. Absent that, you have a bonafide known issue.

Comment #4

cdnsteve CreditAttribution: cdnsteve commented 19 February 2013 at 15:45

I don't believe this is an error or bug related to the Drupal module but has to do with the GSA itself.
We've interfaced with XML with a Java search app as well and I can tell you the number of results pager at the bottom is never correct.

If you even go into the GSA Test Center the results sometimes show 10 pages, if you click on 10, there are actually only 2 pages in the results.

Comment #5

iamEAP CreditAttribution: iamEAP commented 4 November 2015 at 01:22

Issue summary:	View changes
Status:	Postponed (maintainer needs more info)	» Closed (works as designed)

Closing after 3 years of inactivity. I believe the response in #4 is accurate for Internet folks who land here in the future.

Comment #6

AaronBauman

he/him

CreditAttribution: AaronBauman commented 3 May 2016 at 16:04

Title:	Results pager shows too many pages	» Results pager shows "no results" when it should show last page of results
Status:	Closed (works as designed)	» Active

Re-opening because there is some mis-information on this thread, and the paging behavior is still somewhat jarring.

By default, a GSA query is filtered.
You know how you see those "more results from [section]" or "X similar results hidden"?
Those all count in the total number returned from your GSA, even if they're not included in the actual result set returned by your queries.
Automatic filtering applies regardless of the public/private status of your results.

see: https://www.google.com/support/enterprise/static/gsa/docs/admin/72/gsa_d...
and https://www.google.com/support/enterprise/static/gsa/docs/admin/72/gsa_d...

In either case, this module ~~should~~ does conform to the behavior of the GSA:

If the Google Search Appliance has fewer results than the number requested in the search request, the last page of results is returned. The last page is determined by dividing the total number of results into pages based on the number of results requested.

The pager does behave poorly for more than 1000 results, which is in a separate issue: #2103921: Pager breaks after 1000 items