There are certain situations where it's desirable to be able to alter the internal Boost data before content is written to disk. In my case, the project I'm working on has several URLs which load the exact same markup (with the page display changing via javascript based on the URL), and the requirement is that once any of these URLs are hit that the content be cached for all instances. To accommodate this, a simple drupal_alter() call is needed in the boost.module::boost_exit() function. I'll attach a patch implementing this change shortly.

Comments

emanaton created an issue. See original summary.

emanaton’s picture

Aaaand here's the wee patch.