Closed (fixed)
Project:
Views (for Drupal 7)
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Nov 2008 at 04:32 UTC
Updated:
15 Jun 2009 at 21:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
mfer commentedPoking my head around I see the commented out code in views_plugin_display_block.inc that would provide support. It says there is a core bug that needs to get fixed. Is there an issue on that? If not, a description of the problem? I'm willing to throw a little time and working on this.
Comment #2
swentel commentedSubscribing, I want to help investigating this too.
Comment #3
mfer commentedIt seems if you change the cached setting drupal doesn't pick up that change. See #235673: Changes to block caching mode not caught.
Comment #4
mfer commentedA suggestion.... when views updates the block caching why don't we code views to update the cache field in the block table itself. It seems sort of hackish but is there another way?
Comment #5
swentel commentedOk, after skimming the code, I came up with a patch. It's a (quite dirty) fix which saves the cache setting of a block in the blocks table *if* the block allready exists there. Since display_id & view name can't be changed anymore in an existing view, this should be save afaik. Patch only changes views_plugin_display_block.inc and can the code easily be removed once #235673 gets in.
Comment #6
swentel commentedAnd now with patch
Comment #7
merlinofchaos commentedLooks good to me. Committed. I did not thoroughly test this so anyone watching this may want to poke at it. Make sure it doesn't explode.