[ad_1]
\n<\/p>\n
it should be in time<\/strong> – earlier than script\/style is up for being output to page, otherwise it is too late;<\/p>\n<\/li>\n it should be conditional<\/strong> – otherwise you are loading stuff where you don’t need it and cause performance and functionality issues, for this you need WP environment loaded to late stage.<\/p>\n<\/li>\n<\/ul>\n register<\/strong> – this explains WP details about script\/style and makes it store that info;<\/p>\n<\/li>\n enqueue<\/strong> – (often lumped together with register in one print<\/strong> – this happens when WP processes queue, tries to load something specific for itself or<\/strong> when you explicitly do it with (1)<\/em> (8)<\/em> (9)<\/em> It goes much deeper, but this is simple and good enough for important points:<\/p>\n you can get away with queuing scripts (not styles) for footer at any point before Well, the functionality there is even more complex, elaborate and nested.<\/p>\n for starters just use when you need something complex – look through There’s a specific hook named The three stages of the process<\/h2>\n
\n
wp_enqueue_*()<\/code> call) – this tells WP to add scripts\/style to the queue, according to its settings (dependencies, header\/footer loading).<\/p>\n<\/li>\nwp_print_*()<\/code> function.<\/p>\n<\/li>\n<\/ol>\nFront-end structure of functions and hooks<\/h2>\n
\n
wp_head()<\/code><\/p>\n\n
wp_head<\/code><\/p>\n\n
wp_enqueue_scripts()<\/code><\/p>\nwp_enqueue_scripts<\/code> \u00ab this is what you need<\/strong><\/p>\n<\/li>\nwp_print_styles()<\/code><\/p>\n<\/li>\nwp_print_head_scripts()<\/code><\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\nwp_footer()<\/code><\/p>\n\n
wp_footer<\/code><\/p>\n\n
wp_print_footer_scripts()<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n
wp_enqueue_scripts<\/code> is most appropriate hook for registering and queuing scripts and styles on front end<\/strong> and it is there specifically for that;<\/p>\n<\/li>\ninit<\/code> has nothing to do with this, it will work, but – past Codex recommendation to use only it was incorrect<\/strong>;<\/p>\n<\/li>\nwp_print_footer_scripts()<\/code> call;<\/p>\n<\/li>\nwp_print_*<\/code> hooks are NOT appropriate for register\/queue<\/strong>, they are points in code when output is already happening. They are appropriate for manual\/custom script\/style output.<\/p>\n<\/li>\n<\/ul>\nWhat about admin?<\/h2>\n
\n
admin_enqueue_scripts<\/code> hook<\/strong> (it gets passed $hook_suffix<\/code> global for conditional stuff<\/strong>) for everything, it will do nicely for most cases;<\/p>\n<\/li>\nadmin-header.php<\/code> and dig from there for appropriate hooks.<\/p>\n<\/li>\n<\/ul>\nWhat about login?<\/h2>\n
login_enqueue_scripts<\/code>.<\/p>\n<\/p><\/div>\n