I've submitted this report to the Custom Pagers Module as well, but I *think* it's an issue with blockcache.

I'm using views, and the front page module. I've created a view specifically for the front page that inserts the latest node of a webcomic. The node uses custom pagers to allow people to browse through the entire series of comics.

When the standard view is displaying on the front page, the css for the custom pagers module displays correctly. When the blockcache version of the view is displayed, however, all of the css for the custom pagers module is stripped away -- but the css for the rest of the content in the view appears to display normally.

When I go into the blocks admin area and save the blockcache (which I believe is supposed to refresh the cache for that block), and then return to the front page, the custom pagers display correctly. However, when I reload the page, the styles for the custom pagers is once again removed.

I'm assuming (and I may be wrong) that the first time I view the node after refreshing the cache for that block I'm actually viewing the uncached version, because someone needs to view it once before the cache can be generated. When I refresh the page, I'm actually viewing the cached version, and thats when the styles are stripped away. That's what leads me to believe that it's blockcache that is causing the problem.

I hope I explained that clearly. I'm not familiar with the ins and outs of how all the modules interact with each other so I'm not sure my deductions are correct. If you like, I can follow up this post with before and after screenshots to further illustrate what I'm talking about.

Comments

add1sun’s picture

Status: Active » Closed (duplicate)

Closing old issues and pointing this another CSS/theme issue already in the queue, #112727: Address CSS/theme issues when caching