Action hooks in Wordpress - Step-by-Step Execution

Concept Flow - Action hooks

WordPress loads core

↓

Action hook triggered

↓

Check for functions hooked

↓

No hooked functions

↓

Continue normal flow

↓

Continue normal flow

WordPress runs its core, triggers an action hook, then runs all functions attached to that hook before continuing.

Execution Sample

Wordpress

<?php
add_action('init', 'say_hello');
function say_hello() {
  echo 'Hello!';
}
?>

This code attaches a function to the 'init' action hook that prints 'Hello!' when WordPress initializes.

Execution Table

Step	Action Hook Triggered	Hooked Functions Found	Function Executed	Output
1	init	say_hello	say_hello()	Hello!
2	wp_footer	none	none
3	shutdown	none	none

💡 No more hooks triggered, WordPress finishes loading.

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
hook	none	init	wp_footer	shutdown
functions_hooked	none	['say_hello']	[]	[]
output	""	"Hello!"	"Hello!"	"Hello!"

Key Moments - 2 Insights

Why does 'say_hello' run only when the 'init' hook triggers?

Because in the execution_table at Step 1, the 'init' hook triggers and WordPress finds 'say_hello' hooked to it, so it runs. Other hooks have no functions hooked.

What happens if no functions are hooked to an action?

As shown in Steps 2 and 3 in the execution_table, WordPress triggers the hook but finds no functions, so it continues without output or changes.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output after the 'init' hook runs?

A "Hello!"

B "Goodbye!"

C "" (empty)

D "Init hook triggered"

💡 Hint

Check Step 1 in the execution_table under Output column.

At which step does WordPress find no hooked functions?

A Step 1

B Step 2

C Both Step 2 and Step 3

D Step 3

💡 Hint

Look at Hooked Functions Found column in the execution_table.

If we add a function hooked to 'wp_footer', what changes in the execution_table?

A Step 1 output changes

B Step 2 will show the function executed and output updated

C Step 3 will show the function executed

D No changes at all

💡 Hint

Adding a hooked function affects the step where that hook triggers, see Step 2 in execution_table.

Concept Snapshot

Action hooks let you run your code at specific points in WordPress.
Use add_action('hook_name', 'your_function') to attach your function.
When WordPress triggers that hook, your function runs.
If no functions are hooked, WordPress continues normally.
Hooks help customize behavior without changing core files.

Full Transcript

Action hooks in WordPress are points where the system pauses and runs any functions you have attached. When WordPress loads, it triggers hooks like 'init' or 'wp_footer'. If you have used add_action to attach a function to a hook, WordPress runs that function at that moment. For example, attaching 'say_hello' to 'init' makes WordPress print 'Hello!' when it initializes. If no functions are attached to a hook, WordPress just continues without changes. This lets you add or change behavior safely and cleanly.

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