In short - my cache is not being emptied even when I have it set to empty on node add or edit; the cron is run with Rules on the events.

I have a specific use case:
- one of my nodes (lets call it "nodepanel") is overwritten by a panel's node preset to give it nice styling
- the panel, which overwrites the nodes, has some static content in the top and dynamic in the bottom
- the dynamic part is done with Tabs + Tabs panel style
- in each of the Tabs, there is a View giving a result of referenced nodes
Therefore when I am on the node, I see a panel, which in top has static pulled content and dynamic tabs content in the bottom. To better understand what I am talking about, see this page - http://zakrsly-kralicek.cz/uzivatel/luci/kralik-beruska

The thing is, when I add or edit a new photo or video (located in the tabs area), all the associated Views are properly regenerated and therefore properly cached for anonymous users instantly. (my mane page is also using Panels with Views and the page is refreshed fine). If the View, however, resides in the tabbed part, it is not refreshed. I am not using any panel's caching.

This seems to be bug to me but I don't know whether it's more related to Boost, Tabs or Tabs panel style.

Comments

kunago’s picture

kunago commented

Thinking about it again, could the issue be caused by a View using an argument?

The View that is being concerned (the one in tab) is being referenced by a node id. Therefore if Boost is set to clear all Views that have something to do with the node being saved, could the argument be the cause? Maybe Boost does not check for Views with arguments because it would be resource consuming to check all the possible combinations ... just a guess.

I assume all this might be a little bit confusing so if someone needs more details, please let me know.

mikeytown2’s picture

mikeytown2 commented

try the latest dev; it *might* work better for your use case. And yes views argument handling is not currently supported in a good way for new node triggering views expiration; in fact with the latest dev I ignore views that use % in the path. you can enable it though. What I need to do is record the arguments that get used so I can "play them back" when I run all views.

kunago’s picture

kunago commented

Just a thought maybe but could Boost do this?
1) read the array of all Views with arguments
2) compare the list with url's in boost_cache table
3) if it finds a match then flush the page

mikeytown2’s picture

mikeytown2 commented

That kills too many pages for large sites. I have issues with too many view pages getting flushed as it is right now.