Hi Amity,
Minimee attempts to minify HTML at the template_post_parse hook provided by EE, which happens after EE saves a template in the cache. You can verify this by clearing EE’s cache, and then hit a page once and then look in system/expressionengione/cache/page_cache/, there will be a folder with a hash name and then inside that a file; it should contain the (mostly) processed response from EE, and the HTML will NOT be minified.
However, Minimee still is “allowed” to run on the template_post_parse hook, even for templates that have been cached, which it should do whether or not the extension is installed or not.
If you turn on EE’s template debugging, Minimee outputs logging messages at every major step of execution - every message starts with one of:
"Minimee [INFO]..." "Minimee [ERROR]..." "Minimee [DEBUG]..."
At the stage of HTML minification, the message will either be:
"Minimee [INFO]: Running HTML minification." "Minimee [INFO]: HTML minification is disabled."
So if you can turn on the debugging, and hit your page on both cold & warm cache states, see what Minimee is reporting that it’s trying to do - Minimee actually does throw a few other logging messages that are related to the processing flow around HTML minification, so it might be best to search for every instance of “Minimee [” in the debugging output.
If there is no mention either way of MInimee running HTML minification, then it’s likely a hook conflict - see if any other plugins operate on that same template_post_parse hook.
Cheers,
John
p.s. If you have the handy extension EE Debug Toolbar installed, then when debugging is on Minimee will add it’s own panel to the debug toolbar with only it’s log messages isolated.
|