Portal-wide rules and purging cache

While working on some portal-wide rules I found several instances where PageBlaster's cache wasn't purged. In many cases I didn't expect that it should have been such as me editing the skin.css file. In other cases I thought that PB should have noticed. For example, when I edited the content of a Text/Html module I expected that PB might be able to tell and purge that page's cache.

When PB is enabled and something doesn't appear to have taken effect, I am left with disabling PB in the web.config, purging the disk cache directory and re-enabling PB in web.config.  Is there an easier way?

Two suggestions. First, document what cases that PB should be bright enought to purge a page from cache or purge the whole cache. When I workon page replacement rules I disable caching, but there is no way from the user interface to either disable portal-wide caching or to purge the cache. I think both would be useful.

Happy New Year,

/DaveS

PageBlaster automatically clears it's page cache when a post-back is made to a specific page.  The assumption being that if there is data in a post then it is likely an update in some aspect.

What usually happens when it doesn't appear that an update happened is that the module in question has a cache time set. This will cache just that module in the DNN cache. If you disable PageBlaster by changing web.config then that will also clear the DNN cache because the app will restart and it will seem as if disabling PageBlaster cleared the cache, but PageBlaster does not clear it's disk cache on just an app restart.

If you watch the PageBlaster disk cach folder you can see if the updates are clearing the cache.  You can also clear both memory and disk cache for a single page by just deleting the files in a specific tab folder. 

You can also manually clear the PageBlaster cache for a specific page at any time by holding CTRL in IE or SHIFT in FireFox and refreshing the page.  This is the same way you clear your local cache.

You can clear the PageBlaster cache completely without restarting the app by deleting all files in the cache folder.  Or by setting the Snapsis.PageBlaster.config file disk and memory intervals to all zeros.

I'll look into putting a clear cache button into the next version of PageBlaster, but the manual CTRL+Refresh is by far the easiest way to clear a page in my opinion.