Hi, my intension is to have a cached view frontpage that clears immediately when new nodes are created or updated. I enabled this module and configured a view to clear it's cache when any node type ist created or updated. How ever the view shows me cached data no matter if nodes have changed or not. I set min and max cache lifetime to none as well, so the view display can be as current as posible with no minimum restriction. What am I doing wrong?

CommentFileSizeAuthor
#5 views_content_cache-1004072.patch8.54 KBsteven jones

Comments

Anonymous’s picture

Same issue over here.

Instead when content is added (published) paged views lose all pages > 1 and some views will only output a single node instead of six as configured. When that is the case even manually clearing the views' cache (via views extra settings) does not help. I have to pick a view, pretend to cahnge something and save it again. After that all views seem to display correct and current data.

My views are set to do no query caching at all and output cache min lifetime is set to none, max lifetime to 6 hours.

designcontext’s picture

Maybe the standard values are not correct:
I changed nothing and it has:
query min none
query max none
output min 6h
output max 6h
I think it should be none/6h/none/6h

tried it and doesn't work...

steven jones’s picture

Status: Active » Needs work

This needs a test for this simple case.

steven jones’s picture

Title: Views output doesn't update? » Views caching doesn't work with pagers

I've added a test for this now over at, #951080: Tests.

Setting to the issue in the first comment.

steven jones’s picture

Status: Needs work » Reviewed & tested by the community
StatusFileSize
new8.54 KB

Caching does work with pagers. Test attached.

steven jones’s picture

Status: Reviewed & tested by the community » Fixed
les lim’s picture

Version: 6.x-2.2 » 6.x-2.x-dev
Status: Fixed » Closed (duplicate)

I ran into this as well using the Jan 24 2011 dev, but it's probably Views, not Views content cache:

#550962: Caching query results but not rendered output breaks pager

Marking as duplicate here.

mstrelan’s picture

I also still experienced this using Jan 24 2011 dev. I can resolve it by flushing cache, so I'm now trying the patch mentioned in #7 and will see if it stays resolved.