Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Use case is you have an unfiltered, paged listing of nodes, say 10 pages worth. When you click on a BEF filter link, it has the current pager index in it (say page 10). If the filtered results generate only 5 pages of nodes, then you wind up with an empty page with nothing but a pager element in it.
The patch below unsets the pager index when generating the BEF filter links. It only applies properly to beta1 (the verison I'm working with on a production site), but is a simple enough change to be manually applied to any other release.
Comment | File | Size | Author |
---|---|---|---|
#3 | bef-pager_index_not_reset-1924822-3.patch | 521 bytes | GrapefruitJuice |
Comments
Comment #1
arpieb CreditAttribution: arpieb commented... and here's the patch
Comment #2
arpieb CreditAttribution: arpieb commentedComment #3
GrapefruitJuice CreditAttribution: GrapefruitJuice commentedNew patch for 7.x-3.0-beta4 version.
Comment #4
pmchristensen CreditAttribution: pmchristensen commentedThis patch works like a charm and should be included in the project right away. Do not see any use case where which shouldn't be done.
Comment #5
mikeker CreditAttribution: mikeker commentedCommitted. Thank you for the patch!