Generate add_action and add_filter hooks with callback stubs
Start typing to see common hooks
Function name that will be called
Lower numbers = earlier execution (default: 10)
How many parameters the callback accepts
<?php
/**
* Callback for init hook
* @param mixed $arg1
*/
function my_custom_callback($arg1) {
// Perform action
// TODO: Add your logic here
}
<?php
/**
* Hook: init
*/
add_action('init', 'my_custom_callback');
💡 Usage: Add this code to your theme's functions.php or plugin file
Execution Order:
Actions allow you to execute code at specific points in WordPress execution.
• Don't return values
• Used for side effects (save data, send email, etc.)
• Example: init, wp_enqueue_scripts, save_post
Action Hooks: Execute code at specific points (wp_footer, save_post). Use for side effects - sending emails, logging, triggering operations.
Filter Hooks: Modify data before use (the_content, post_title). MUST return modified value. Use for data transformation.
1. Select Hook: Choose from 50+ common WordPress hooks or enter custom hook name. Tool provides autocomplete suggestions.
2. Function Name: Enter unique callback function name. Use prefix to avoid conflicts (myplugin_custom_footer).
3. Set Priority: Default 10. Lower numbers (5) run first, higher (20+) run later. Use when execution order matters.
4. Arguments: Specify how many parameters your callback accepts. Check WordPress documentation for hook signature.
5. Generate Code: Creates complete add_action/add_filter registration with properly structured callback function stub.
Filters must return value. Actions don't return. Check hook documentation for available parameters and execution context.
Actions execute code at specific points (like publishing a post) without returning values. Filters modify data before use (like changing post content) and must return the modified value. Use actions for side effects, filters for data transformation.
Priority determines execution order (default: 10, lower runs first). Use lower priority (5) to run before others, higher (20+) to run after. Most hooks work fine at default 10. Change priority when you need to ensure execution order relative to other code.
Match the parameters provided by the hook you're using. Check WordPress documentation for each hook. Common patterns: 1 param for simple filters, 2-3 for context data, more for complex operations. This tool generates the correct function signature.
Name clearly with prefix: do_action('myplugin_after_save'). Provide useful parameters. Document what data is passed. Use consistent naming patterns. Actions for events, filters for data modification. This makes your plugin/theme extensible for other developers.