Strategy 4: Reusable Function

The fourth strategy is to encapsulate the functionality and abstract it away to a reusable function within your child theme. Let’s do this together.

While you could add this function to your child theme’s functions.php file, it’s better to build your theme’s in a modular format.

Best Practice – Modular Approach

Using a modular approach, you will create a folder in the theme’s lib folder and call it structure. Then in the {child theme}/lib/structure folder, create a new file called footer.php. Here is the code that removes the site footer for each of the pages that you specify:

Namespace code example

Here is the namespace approach. I built everything in a modular, packaged architecture, which means I use PHP Namespace.

	<?php
	/**
	* Footer HTML Structure Functions
	*
	* @package KnowTheCode\Structure
	* @since 1.0.0
	* @author hellofromTonya
	* @link https://KnowTheCode.io
	* @license GNU-2.0+
	*/
	namespace KnowTheCode\Structure;
	add_action( 'genesis_before_footer', __NAMESPACE__ . '\remove_site_footer_from_specific_pages' );
	/**
	* Remove the site footer from the specified pages.
	*
	* @since 1.0.0
	*
	* @return void
	*/
	function remove_site_footer_from_specific_pages() {
	if ( ! is_home() || ! is_front_page() ) {
	return;
	}
	//remove_action( 'genesis_footer', 'genesis_footer_markup_open', 5 );
	//remove_action( 'genesis_footer', 'genesis_footer_markup_close', 15 );
	//remove_action( 'genesis_footer', 'genesis_do_footer' );
	remove_all_actions( 'genesis_footer' );
	}

view raw

footer.php

hosted with ❤ by GitHub

Prefixed code example

Here is the prefixed approach for the same code. You would change the prefix to what you are using in your child theme, i.e. change prefix_ to ktc_ or whatever you are using.

	<?php
	/**
	* Footer HTML Structure Functions
	*
	* @package KnowTheCode\Structure
	* @since 1.0.0
	* @author hellofromTonya
	* @link https://KnowTheCode.io
	* @license GNU-2.0+
	*/
	add_action( 'genesis_before_footer', 'prefix_remove_site_footer_from_specific_pages' );
	/**
	* Remove the site footer from the specified pages.
	*
	* @since 1.0.0
	*
	* @return void
	*/
	function prefix_remove_site_footer_from_specific_pages() {
	if ( ! is_home() || ! is_front_page() ) {
	return;
	}
	//remove_action( 'genesis_footer', 'genesis_footer_markup_open', 5 );
	//remove_action( 'genesis_footer', 'genesis_footer_markup_close', 15 );
	//remove_action( 'genesis_footer', 'genesis_do_footer' );
	remove_all_actions( 'genesis_footer' );
	}

view raw

footer.php

hosted with ❤ by GitHub

You’ll need to load this new file into your theme by adding the following line of code to your theme’s function.php file:

include_once( __DIR__ . '/lib/structure/footer.php' );

I want to put it in my functions.php

Okay, if you prefer to put it into your functions.php file instead of using the modular approach, here is the code for you. Just change the prefix to what you are using.

Prefixed code example

	// put this function at the bottom of your theme's
	// function.php file
	add_action( 'genesis_before_footer', 'prefix_remove_site_footer_from_specific_pages' );
	/**
	* Remove the site footer from the specified pages.
	*
	* @since 1.0.0
	*
	* @return void
	*/
	function prefix_remove_site_footer_from_specific_pages() {
	if ( ! is_home() || ! is_front_page() ) {
	return;
	}
	//remove_action( 'genesis_footer', 'genesis_footer_markup_open', 5 );
	//remove_action( 'genesis_footer', 'genesis_footer_markup_close', 15 );
	//remove_action( 'genesis_footer', 'genesis_do_footer' );
	remove_all_actions( 'genesis_footer' );
	}

view raw

functions.php

hosted with ❤ by GitHub

When to Use this Approach?

You use this approach when you will have multiple pages where you want to remove the site footer. For example, let’s say you want to remove the site footer on the Posts’ Page, Front Page, About, Contact, Archives, etc. Then you can use this strategy.

Otherwise, it’s a better approach to use strategy 2 or 3. Why? Because this function gets called for every single web page on your website. Every single one. It’s always going to call this function and then check if it’s the right page. It’s a little slower than strategy 2 and 3. It’s also a little more confusing.