Support Forum

login_head is to used to let plugins or themes hook into the login form process... without it, anything that needs to hook into login form processing, may not be able too... might not be an issue for your site...

but your code change is pointless as made... you would be better off removing the line of code... as you changed it, you will just be wasting cpu cycles...

so, yeah, like I thought its the inline login form... oddly, not quite the way I thought though... think this is the first time we have run into a plugin that is loading js via that hook (which it probably should be able to) that is causing problems... loading js in the middle of the page is technically not correct, but can work...

in this situation, your theme or plugin is still not loading the js correctly... and our use of that action has exacerbated the problem... so what happens is gantry is trying to load the mootools js in the head tags via that action... when we call it later, it loads it later... this causes problems for other js that has a dependency on the mootools... so really, gantry should be specifying those dependencies since the wp enqueue stuff supports it... in other words it should load the js that depends on the js loaded in the login_head action after the needed js is loaded... they just made an assumption it would be loaded.. assumptions like that are bad the fact that we fired the hook in the body instead of the head tags, made the issue come to light...

so it would be nice if gantry would use the wp js loading api and specify dependencies rather than blanket loading stuff and making assumptions.. Frankly, the api is there for a reason...

that said, on the other hand, we need to take a look at our use of that action too since its really supposed to be in the page head tags so plugins/themes can load js... we may want to clean up our end too...