Head & Footer Code vs Scripts To Footer

Head & Footer Code plugin helps you add custom code snippets (JavaScript, CSS, or HTML) to the page even if you are not a programmer. It could be within the (site verification code for various services, custom styles, meta or Webfont link), right after opening (pixel tracking, analytics or heatmap code) or just before closing tag. Go to Tools → Head & Footer Code in WordPress Dashboard. Insert custom code to HEAD, BODY or FOOTER section (depending on what you have to do). All magic is done by hooking to WordPress hooks wp_head, wp_footer and wp_body_open. 💡 Trial Head & Footer Code plugin on a free dummy website before you add it on your project: Test It Now! Various code snippets are supported, including but not limited to: Google Analytics 4 Google Tag Manager Google Ads Conversion Lite Analytics Facebook/Meta Pixel Hotjar FullStory Google site verification Bing site verification Yandex site verification Alexa site verification Homepage in Blog Posts mode If your WordPress shows the latest blog posts on the homepage, you can also add specific code only for the homepage on Tools → Head & Footer Code (there will be section Head, body and footer code on Homepage in Blog Posts mode) Article specific code To insert custom code specific for individual article (post, page or custom post type), use article-specific Metabox while editing post/page/custom post type (check out Screenshots). There choose if that specific code appends to site-wide code defined on Tools → Head & Footer Code, or to replace it. Category specific code You can also define a Category specific code on each individual category. Other taxonomies (tag and custom taxonomy) do not have available their specific code, but for them a Global code is used instead. Video guide Do you need our support? If Head & Footer Code does not work on your project, please let us know by raising a new support ticket in the Community Forum and describe what does not works and how to reproduce the issue. We will make sure to resolve the issue as soon as possible. If you find Head & Footer Code useful for your project, please review plugin. Features Multisite and PHP 8.5 compatible! Set site-wide custom content for: head page section (before the ) body section (after the ) – Requires WordPress 5.2! footer page section (before the ) Homepage in Blog Posts mode: set homepage specific custom code for head, body and/or footer toggle homepage specific custom code on paged Homepage (page 2, 3, a nd so on) Set article specific custom code for: head page section (before the ) body section (after the ) – Requires WordPress 5.2! footer page section (before the ) Set category specific custom code for head, body and/or footer of the page Choose priority of printed custom code to head/body/footer sections (lower number mean far from and and closer to , higher number means closer to and and farther to ) Choose which post types will have enabled article specific head/body/footer fields Choose should article specific head/body/footer code be appended to site-wide code, or will replace site-wide code View on Posts/Pages/Custom Post Types listing if article has defined any article specific custom code Site-wide section is located under Tools > Head & Footer Code If you have set WP_DEBUG constant in wp-config.php to true, you’ll see site-wide and article specific entries in page source code wrapped to comments. [NEW] allow unprivileged user roles Editor and Author to manage article-specific code on single site and multisite (disabled by default) Data stored in database General settings (HEAD, BODY, FOOTER global code and priority, Homepage code and behaviour) saves in WordPress option auhfc_settings. Each post/page/custom post type specific HEAD, BODY and FOOTER code and behaviour saves to post meta _auhfc. Each category specific HEAD, BODY and FOOTER code and behaviour saves to taxonomy meta _auhfc. During the Uninstall process all these data has been deleted from the database. In case you wish to reinstall plugin, DO NOT UNINSTALL IT although Deactivate, then delete the directory /wp-content/plugins/head-footer-code and then reinstall plugin. Permissions on Multisite WordPress Access to Global: only Super Admin and Administrator Access to Article specific: Super Admin, Administrator; optional: Editor and Author Access to Category specific: only Super Admin and Administrator

This small plugin moves scripts to the footer. Note that this only works if you have plugins and a theme that utilizes wp_enqueue_scripts correctly. You can disable the plugin on specific pages and posts directly via the post/page edit screen metabox. You can disable the plugin on specific archive pages (blog page, search page, post type and taxonomy archives) via the settings page. Everything Broken? Try placing jQuery back into the header via Settings > Scripts to Footer, “Keep jQuery in the Header” checkbox. If that doesn’t work, refer to the walkthrough below for using the stf_exclude_scripts filter for the script that is causing the issue. Check out the documentation on GitHub or some quick walkthroughs below. Keeping specific Scripts in the Header As of version 0.6 you can now keep specific scripts in the header. Note: this will print any scripts they depend on as well (if you want to keep jquery-effects-core in the header, you’ll also get jQuery in the header, so no need to add both). Specifically for jQuery, see the settings page option, as it is a common request we’ve built it into the settings. For any other scripts, use this filter: add_filter( 'stf_exclude_scripts', 'jdn_header_scripts', 10, 1 ); function jdn_header_scripts( $scripts ) { $scripts[] = 'backbone'; // Replace 'backbone' with the script slug return $scripts; } You will need the correct script slug, which is used when the script is registered, and the script will only be printed into the header if it’s enqueued. Check out the scripts that come registered out-of-the-box with WordPress. Note: As of version 0.6.3, conditional tags will work with the stf_exclude_scripts filter. Custom Post Type Support If you’re comfortable with code you can use the scripts_to_footer_post_types filter to change the post types this applies to (it only applies to pages and posts by default). For example, if you have a custom post type called “project” you could add support for this metabox via the post type filter like this: function stf_add_cpt_support( $post_types ) { $post_types[] = 'project'; return $post_types; } add_filter( 'scripts_to_footer_post_types', 'stf_add_cpt_support' ); Excluding Pages/Posts/Templates Via Filter You can either use the checkbox option to disable the plugin’s action on a specific page/post, or you can utilize a filter. The filter also passes the post/page id, if there is one (archive templates don’t have ids!). For example, for the “page” post type: function stf_exclude_my_page( $exclude_page, $post_id ) { if ( is_front_page() ) { $exclude_page = 'on'; // this turns on the "exclude" option } return $exclude_page; } add_filter( 'stf_page', 'stf_exclude_my_page' ); Replace stf_page with stf_post for posts, or the slug of your custom post type. For instance, a post type called “project” can be filtered with stf_project. More Documentation See the plugin’s wiki. Development / Contributing View this plugin on GitHub. Support Please feel free to open a Github Issue to report conflicts or goto the WP.org support forum. If there is something wrong with Scripts-to-Footer, we’ll update it. However, if it’s a another plugin or theme we can only contact the developer with the issue to attempt to resolve it.