Action hooks in Wordpress

Introduction

Action hooks let you add your own code at specific points in WordPress without changing core files. They help you customize how WordPress works safely.

You want to run code when a post is published.

You want to add extra content to the footer of your site.

You want to send an email when a user registers.

You want to modify how WordPress loads scripts or styles.

You want to log information when a comment is posted.

Syntax

Wordpress

add_action('hook_name', 'your_function_name', priority, accepted_args);

function your_function_name() {
    // Your code here
}

hook_name is the name of the action point in WordPress.

priority controls the order your function runs (default is 10).

accepted_args is the number of arguments your function accepts (default is 1).

Examples

This adds a message at the bottom of every page in the footer.

Wordpress

add_action('wp_footer', 'add_footer_text');

function add_footer_text() {
    echo '<p>Thank you for visiting!</p>';
}

This runs when a post is published, with priority 20.

Wordpress

add_action('publish_post', 'notify_admin_on_publish', 20);

function notify_admin_on_publish($post_ID) {
    // Code to send email to admin
}

This runs when a new user registers, receiving the user ID as argument.

Wordpress

add_action('user_register', 'welcome_new_user', 10, 1);

function welcome_new_user($user_id) {
    // Send welcome email to new user
}

Sample Program

This code adds a centered gray message at the bottom of every page using the wp_footer action hook.

Wordpress

<?php
// Add a message to the footer
add_action('wp_footer', 'show_footer_message');

function show_footer_message() {
    echo '<p style="text-align:center; color: gray;">Powered by WordPress Action Hooks</p>';
}
?>

Important Notes

Action hooks do not change content directly; they let you run code at certain points.

Always use unique function names to avoid conflicts.

You can remove an action with remove_action() if needed.

Summary

Action hooks let you add custom code at specific points in WordPress.

Use add_action() with a hook name and your function.

They help customize WordPress safely without editing core files.

Practice

1. What is the main purpose of an action hook in WordPress?

easy

A. To create new database tables automatically

B. To let you add custom code at specific points without changing core files

C. To style the website using CSS

D. To replace WordPress themes entirely

Solution

1. Step 1: Understand what action hooks do

   Action hooks allow you to insert your own code at certain points in WordPress execution.

2. Step 2: Recognize safe customization

   This lets you customize WordPress without editing its core files, which is safer and update-proof.

3. Final Answer:

   To let you add custom code at specific points without changing core files -> Option B

4. Quick Check:

   Action hooks = safe custom code insertion [OK]

Hint: Action hooks add code safely without core file changes [OK]

Common Mistakes:

• Thinking action hooks create database tables
• Confusing action hooks with styling tools
• Believing action hooks replace themes

2. Which of the following is the correct syntax to add a function to an action hook in WordPress?

easy

A. add_action('init', my_function());

B. add_action(my_function, 'init');

C. add_action('init', 'my_function');

D. add_action('my_function', init);

Solution

1. Step 1: Recall add_action syntax

   The first argument is the hook name as a string, the second is the function name as a string.

2. Step 2: Check each option

   add_action('init', 'my_function'); matches the correct syntax: add_action('hook_name', 'function_name'); others mix argument order or call the function immediately.

3. Final Answer:

   add_action('init', 'my_function'); -> Option C

4. Quick Check:

   Hook name first, function name second as strings [OK]

Hint: Hook name and function name are strings in add_action() [OK]

Common Mistakes:

• Swapping hook and function arguments
• Passing function call instead of function name
• Not using quotes around function name

3. What will be the output of this code snippet?

function greet() {
  echo 'Hello!';
}
add_action('wp_footer', 'greet');

Assuming the theme calls do_action('wp_footer'); in the footer.

medium

A. The text 'Hello!' will appear in the footer

B. Nothing will be displayed

C. A PHP error will occur

D. The text 'greet' will appear in the footer

Solution

1. Step 1: Understand add_action and do_action

   add_action attaches 'greet' function to 'wp_footer' hook. When do_action('wp_footer') runs, it calls 'greet'.

2. Step 2: Analyze the greet function output

   The greet function echoes 'Hello!', so this text will appear where the footer hook runs.

3. Final Answer:

   The text 'Hello!' will appear in the footer -> Option A

4. Quick Check:

   do_action triggers greet, which echoes 'Hello!' [OK]

Hint: do_action runs hooked functions, output appears where called [OK]

Common Mistakes:

• Thinking nothing happens without explicit call
• Confusing function name string with output
• Expecting errors from correct hook usage

4. Identify the error in this code snippet:

function add_custom_text() {
  echo 'Custom Text';
}
add_action('init', add_custom_text());

medium

A. The function add_custom_text is not defined

B. The hook name 'init' is invalid

C. Missing semicolon after function definition

D. The function add_custom_text is called immediately instead of being hooked

Solution

1. Step 1: Check how add_action expects arguments

   add_action expects the second argument as a function name string, not a function call.

2. Step 2: Identify the mistake in the code

   Using add_custom_text() calls the function immediately and passes its result, which is incorrect.

3. Final Answer:

   The function add_custom_text is called immediately instead of being hooked -> Option D

4. Quick Check:

   Pass function name as string, not call it [OK]

Hint: Use function name string, not function call in add_action() [OK]

Common Mistakes:

• Calling function instead of passing name
• Assuming hook name is wrong
• Missing semicolon confusion

5. You want to add a custom message only after the WordPress footer content is fully loaded, but only on single post pages. Which code snippet correctly uses an action hook with a condition?

hard

A. add_action('wp_footer', function() { if (is_single()) { echo 'Thanks for reading!'; } });

B. add_action('init', function() { if (is_single()) { echo 'Thanks for reading!'; } });

C. add_action('wp_head', function() { if (is_single()) { echo 'Thanks for reading!'; } });

D. add_action('wp_footer', function() { echo 'Thanks for reading!'; });

Solution

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

   'wp_footer' runs after footer content loads, so it's the right hook to add footer messages.

2. Step 2: Apply condition to show message only on single posts

   Using is_single() inside the hooked function ensures the message appears only on single post pages.

3. Final Answer:

   add_action('wp_footer', function() { if (is_single()) { echo 'Thanks for reading!'; } }); -> Option A

4. Quick Check:

   Footer hook + condition inside function = correct usage [OK]

Hint: Use wp_footer hook with is_single() condition inside function [OK]

Common Mistakes:

• Using init or wp_head hooks for footer content
• Not adding condition for single posts
• Echoing outside hooked function