Very excited about the philosophy and rapid progression of the Hummingbird plugin just like all the great work currently being done by WPMUDEV.
(Cant wait to get my hands on a stress ball! ;-P)
However, we are experiencing some weird results and without understanding exactly what the plugin is trying to do we are left bewildered by some situations.
There is no hard documentation for this plugin - and I can't think why you would need to - other than to give us a bit more understanding about what SHOULD be happening so we can then maybe dig a little deeper but at this stage it seems some things arent totally ironed out. Not unreasonable considering the freshness of the plugin.
Not all files seem to be displayed when going to Minify. (Lists 17 files to be enqueued then dashboard says 18 are being enqueued? Then output under the minification settings only shows 15 files?) I have a gut feeling this is something to do with the updates as we have had all the versions of this plugin installed at some point. It used to shows us a login.css file which has disappeared - once I find it I will let you know what it was - basically it affects our wp-login css which is customized via another plugin.
I was going to write a small plugin to list what is being enqueued by wordpress (im guessing hummingbird does this in order to do its job) so I could compare the two. I know part of the initial file check is supposed to highlight files which can be controlled but then its not clear what effect removing the 'include' option does. Does that file still load as normal just not with everything else or does 'include' not being ticked mean the file will be trashed from the queue?
Clearing minification settings and disabling it still show number of enqueued files on Hummingbird dashboard. Not sure if the meta box is simply skipping on checking if the minification is active and looking directly at database options (not sure what is stored in the database for this plugin - only a guess).
We have seen that sometimes we turn off minification and reload the dashboard only to find it is in fact back on again. Struggling to replicate this again but thought it would worth adding - again perhaps issue with database or updates to the plugin?