This is a curious problem.

I have views, the front page module, and blockcache installed along with custom pager. I have created a view specifically for the front page that displays the latest node of one of my web comics. Custom pagers appears normally on the standard view, displaying all css styles properly.

When I decide to use the block cached version of the view, however, all css styles are removed from the pagers (and only the pagers -- the rest of the block displays normally, as near as I can tell). If I go into the blocks area and save the blockcached version of the view (which deletes the cache), the css styles show properly when I view the block again. But if I refresh the front page, once again the css styles are stripped away from custom pager.

I assume that the first time you view the blockcached view, you're looking at it without cache (because you need to view it once before the cache is created), and that it's the cached version of the view that is screwing up the stylesheets. And if it's the process of building the cache that screws up the stylesheets it's probably a bug in blockcache, not custom pagers. I'm reporting this there as well to cover all bases.

Comments

eaton’s picture

eaton commented

Hmmmm. Yes, that's because it's only adding the .css file when theme('custom_pager'...) is called. Two possible solutions: I could move the CSS inclusion code a central location, where it's included on all pages. Alternately, you can put the CSS rules from custom_pagers.css into your theme's CSS. That will ensure that it's in there regardless of how it's cached.

ubersoft’s picture

ubersoft commented

I added the css rules to my theme's stylesheet, and that seems to have solved the problem.

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Closed (fixed)

In D6 and D7, you can disable block caching within Views or at the module level in hook_block(). I'm closing this out since D5 isn't supported any more.