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.
Problem/Motivation
When using views caching, the results and output is cached without considering the date pager.
Proposed resolution
See attached patch, by adding the pager value to the build_info, we can make sure that views is cached differently for different months, for example.
Note: This currently only works for the results cache, the output cache is cached based on the results, so if you're testing without having something to show in the calendar, then it will be cached incorrectly, see #2454671: Include build info in output cache for that.
Remaining tasks
User interface changes
API changes
Comment | File | Size | Author |
---|---|---|---|
#8 | date-pager-cache-2454667-6.patch | 607 bytes | Berdir |
Comments
Comment #1
BerdirComment #2
dawehnerPatch looks pretty straightforward, if not even trivial.
Comment #3
vijaycs85@Berdir, hope you are testing the testbot with 0 bytes patch :)
Comment #4
BerdirGrml, yeah, yeah, you're all soo funny :p
Comment #6
BerdirAnd another attempt.
Comment #8
BerdirI think I should just go home.
Comment #9
BerdirComment #10
Chris Matthews CreditAttribution: Chris Matthews commentedThe 4 year old patch to date_views_plugin_pager.inc in #8 still applies cleanly to the latest 7.x-2.x-dev and seems like a reasonable/necessary fix to me.