Common action hooks in Wordpress - Mini Project: Build & Apply

Using Common Action Hooks in WordPress

📖 Scenario: You are customizing a WordPress site to add extra content and functionality without changing core files. WordPress uses action hooks to let you run your code at specific points.In this project, you will learn how to use common action hooks to add a message to the site header, enqueue a custom stylesheet, and add a footer note.

🎯 Goal: Build a simple WordPress plugin that uses common action hooks: wp_head, wp_enqueue_scripts, and wp_footer. Your plugin will add a header message, load a CSS file, and show a footer note.

📋 What You'll Learn

Create a function to add a header message using the wp_head action hook

Create a function to enqueue a custom CSS file using the wp_enqueue_scripts action hook

Create a function to add a footer note using the wp_footer action hook

Hook each function to the correct WordPress action

💡 Why This Matters

🌍 Real World

WordPress developers often use action hooks to add or change site features without editing core files. This keeps sites safe and easy to update.

💼 Career

Knowing how to use WordPress action hooks is essential for plugin development and theme customization roles.

1

Create a header message function and hook it to wp_head

Create a function called add_header_message that echoes the HTML <p>Welcome to my WordPress site!</p>. Then hook this function to the wp_head action using add_action.

Wordpress

# Your code here

Hint

Use add_action('wp_head', 'add_header_message') to run your function in the header.

2

Create a function to enqueue a CSS file and hook it to wp_enqueue_scripts

Create a function called enqueue_custom_styles that uses wp_enqueue_style to load a CSS file named custom-style.css located in your plugin folder. Hook this function to the wp_enqueue_scripts action.

Wordpress

Welcome to my WordPress site!';
}
add_action('wp_head', 'add_header_message');

# Your code here

Hint

Use plugin_dir_url(__FILE__) to get the plugin folder URL for your CSS file.

3

Create a footer note function and hook it to wp_footer

Create a function called add_footer_note that echoes the HTML <p>Thank you for visiting!</p>. Hook this function to the wp_footer action.

Wordpress

Welcome to my WordPress site!';
}
add_action('wp_head', 'add_header_message');

function enqueue_custom_styles() {
    wp_enqueue_style('custom-style', plugin_dir_url(__FILE__) . 'custom-style.css');
}
add_action('wp_enqueue_scripts', 'enqueue_custom_styles');

# Your code here

Hint

Hook your footer note function to wp_footer to show it at the bottom of the page.

4

Complete the plugin file with opening PHP tag and comments

Add the opening PHP tag <?php at the top of the file if missing. Add a comment line // Plugin to add header message, enqueue styles, and footer note at the top.

Wordpress

# Your code here

Hint

Start your plugin file with <?php and a comment describing the plugin.

Practice

1. Which WordPress action hook is commonly used to run code after WordPress has finished loading but before any headers are sent?

easy

A. wp_footer

B. wp_head

C. save_post

D. init

Solution

1. Step 1: Understand the purpose of init hook

   The init hook runs after WordPress loads but before headers are sent, ideal for initialization tasks.

2. Step 2: Compare with other hooks

   wp_head and wp_footer run during page rendering, save_post runs on post save, so they don't fit the timing.

3. Final Answer:

   init -> Option D

4. Quick Check:

   Initialization hook = init [OK]

Hint: Remember: init runs early after loading [OK]

Common Mistakes:

• Confusing wp_head with init
• Thinking save_post runs on page load
• Mixing wp_footer timing with init

2. Which of the following is the correct syntax to add a function named my_custom_function to the wp_footer action hook?

easy

A. add_action('wp_footer', my_custom_function);

B. add_action(wp_footer, 'my_custom_function');

C. add_action('wp_footer', 'my_custom_function');

D. add_action('wp_footer', my_custom_function());

Solution

1. Step 1: Check the function name parameter

   The function name must be passed as a string, so quotes are required around 'my_custom_function'.

2. Step 2: Verify the hook name and function call

   The hook name must be a string, so 'wp_footer' is correct. The function should not be called (no parentheses).

3. Final Answer:

   add_action('wp_footer', 'my_custom_function'); -> Option C

4. Quick Check:

   Function name as string, no parentheses [OK]

Hint: Function names in add_action must be quoted strings [OK]

Common Mistakes:

• Passing function name without quotes
• Calling the function with parentheses inside add_action
• Not quoting the hook name string

3. What will be the output when the following code runs in a WordPress theme?

add_action('wp_head', function() { echo '<!-- Header comment -->'; });

medium

A. The code will cause a fatal error due to incorrect hook usage.

B. The comment <!-- Header comment --> will appear inside the HTML <head> section.

C. The comment will not appear because anonymous functions are not allowed.

D. The comment will appear at the bottom of the page before </body>.

Solution

1. Step 1: Understand the wp_head hook timing

   The wp_head hook runs inside the HTML <head> section of the page.

2. Step 2: Analyze the anonymous function output

   The function echoes an HTML comment, so it will be output exactly where the hook runs, inside <head>.

3. Final Answer:

   The comment <!-- Header comment --> will appear inside the HTML <head> section. -> Option B

4. Quick Check:

   wp_head outputs inside <head> [OK]

Hint: Remember wp_head outputs inside <head> tag [OK]

Common Mistakes:

• Thinking output appears in footer
• Believing anonymous functions are disallowed
• Assuming hook causes error

4. Identify the error in this code snippet that tries to save custom data when a post is saved:

add_action('save_post', 'save_custom_data');
function save_custom_data() {
  update_post_meta(get_the_ID(), 'custom_key', 'custom_value');
}

medium

A. The function save_custom_data should accept the post ID parameter.

B. The hook name should be 'save_post_data' instead of 'save_post'.

C. update_post_meta cannot be used inside save_post hook.

D. get_the_ID() returns the wrong post ID inside save_post.

Solution

1. Step 1: Check the save_post hook function signature

   The save_post hook passes the post ID as a parameter to the callback function, so the function must accept it.

2. Step 2: Analyze the function usage of get_the_ID()

   get_the_ID() may not return the correct post ID in this context; the passed post ID parameter should be used instead.

3. Final Answer:

   The function save_custom_data should accept the post ID parameter. -> Option A

4. Quick Check:

   save_post callback needs post ID parameter [OK]

Hint: save_post callback must accept post ID parameter [OK]

Common Mistakes:

• Ignoring the post ID parameter in callback
• Using wrong hook name
• Assuming get_the_ID() works inside save_post

5. You want to add a custom script only on the front page footer using WordPress hooks. Which combination of hooks and conditions is the best approach?

hard

A. Use add_action('wp_footer', 'my_script_function') and inside the function check is_front_page() before outputting the script.

B. Use add_action('init', 'my_script_function') and output the script directly.

C. Use add_action('wp_head', 'my_script_function') without any condition.

D. Use add_action('save_post', 'my_script_function') to add the script on front page.

Solution

1. Step 1: Identify the correct hook for footer scripts

   The wp_footer hook is the proper place to add scripts before the closing </body> tag.

2. Step 2: Use conditional check for front page

   Inside the callback, use is_front_page() to ensure the script runs only on the front page.

3. Final Answer:

   Use add_action('wp_footer', 'my_script_function') and inside the function check is_front_page() before outputting the script. -> Option A

4. Quick Check:

   Footer hook + front page check = Use add_action('wp_footer', 'my_script_function') and inside the function check is_front_page() before outputting the script. [OK]

Hint: Add scripts in wp_footer with is_front_page() check [OK]

Common Mistakes:

• Using init hook to output scripts directly
• Adding scripts in wp_head without condition
• Using save_post hook for front page scripts