Caching doesn't work with pager and exposed filters [#1143476]

I have a page node, with an embedded view (viewfield) that has several exposed filters in a block. The first time the view is loaded, and cached, the pager is cached with whatever filter settings happen to be set at the time. From then on, if I change one of the filters and then use the pager, the filters change back to their cached value.

For example, lets say I have a "Color" filter, which can be Red, Blue, or Green. And lets say the filter is on Red the first time the view is loaded. Then, I change the filter to Green and the view changes. Then I click the pager to advance to the second page. The view will go to the next page, but the filter changes back to Red. If I change the filter to Green, clear the cache, then change the filter to Red and advance the pager, the filter will now revert to Green.

Comment	File	Size	Author
#4	views_content_cache_output_key.patch	1.14 KB	hefox
#4

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

jstoller

he/him

CreditAttribution: jstoller commented 7 May 2011 at 21:31

This seems to be a more general Views issue, since it happens with the time-based cache, as well as content cache. I've posted it in Views issue queue as well.

#1150394: Views caching breaks pager with exposed filters

Comment #2

Equinger CreditAttribution: Equinger commented 26 July 2011 at 20:16

Have you made any headway on this? I'm having trouble on this front as well. I'm trying this with views 3 though.

Comment #3

jstoller

he/him

CreditAttribution: jstoller commented 27 July 2011 at 15:39

@Equinger: I'm afraid not. The code is a bit beyond me. I've been hoping someone on the Views issue queue would take up the case and find a fix, but that hasn't happened yet. You might want to go to that issue and corroborate the problem. The more people experiencing it, the more likely someone will fix it, I expect.

Comment #4

hefox CreditAttribution: hefox commented 9 November 2011 at 23:57

File	Size
views_content_cache_output_key.patch	1.14 KB

Curious, does this patch help at all?

Comment #5

kongoji CreditAttribution: kongoji commented 11 November 2011 at 10:53

patch at #4 works well for me.

Comment #6

hefox CreditAttribution: hefox commented 11 November 2011 at 15:44

If the result of a view is cached, they share the same rendered output currently, even if the exposed filters, etc. are different. This is a views bug that has a seperate issue post.. somewhere. That's the issue this patch fixes, but not sure if it's the same as the issue the OP is experiencing.

Comment #7

Equinger CreditAttribution: Equinger commented 23 January 2012 at 02:25

Thank you Hefox. Important fix.

Comment #8

jstoller

he/him

CreditAttribution: jstoller commented 25 January 2012 at 04:14

Status:

Active

» Reviewed & tested by the community

Awesome! This appears to fix the problem.

@hefox: Should a more general fix be applied to Views? Can your patch be adapted to solve the problem there? The corresponding Views issue is at #1150394: Views caching breaks pager with exposed filters

Comment #9

hefox CreditAttribution: hefox commented 25 January 2012 at 05:16

There's another views issue with a similar patch I believe

Comment #10

ChrisLaFrancis CreditAttribution: ChrisLaFrancis commented 10 February 2012 at 04:53

Status:

Reviewed & tested by the community

» Needs work

I'm still seeing this problem even after applying the patch in #4. If I change to the time-based caching, I don't experience the issue. Not sure if it matters, but I'm also using Boost (6.x-1.x-dev)... adding the view's page's path to the list of exclusions in Boost doesn't seem to make a difference. I'm using Views 6.x-3.0.