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.
I've got a table view page whose pager did not function. It always showed the last page of the set and I could not even get to the previous ones -- the page would just reload on the new path (AJAX off).
Eventually found out that switching off Cache Graceful fixed this behaviour.
So I am afraid there is some bug that prevents paging to work. Tried with the latest stable and dev release for D7. Tried with full and minimal pager.
Comments
Comment #1
gielfeldt CreditAttribution: gielfeldt commentedThanks. I'll look into it.
Comment #2
gielfeldt CreditAttribution: gielfeldt commentedHi Vacilando
I can also reproduce this with the built-in time-based caching. I think it might be due to this bug #1055616: Query arguments should be replaced before generating cache ID
The key used for cache is always the same, regardless of the exposed filters, or the pager.
Perhaps you could try out the patch from the other ticket, and see if it works out? Looks like opinions differ whether or not this patch should be applied. Since it also affects the built-in cache, I don't know why they're hesitant to apply it.
If the patch it doesn't work out, let me know. I might be able to override the get_results_key() method for this cache plugin.
Comment #3
gielfeldt CreditAttribution: gielfeldt commentedActually, I was wrong it seems ... there is a problem with the pager, just like you say. I just mixed it up with my exposed filters. I'll see if I can find a solution.
Comment #4
gielfeldt CreditAttribution: gielfeldt commentedThere! It was just a stupid copy/paste error. Committed to 7.x-1.x. Tarball probably not ready yet ...
Comment #5
Vacilando CreditAttribution: Vacilando commentedYep; works now :-)