WordPress Plugin development

30% OFF - 9th Anniversary discount on Entity Framework Extensions until December 15 with code: ZZZANNIVERSARY9


  • add_action(string $tag, callable $function_to_add, int $priority = 10, int $accepted_args = 1)
  • add_filter(string $tag, callable $function_to_add, int $priority = 10, int $accepted_args = 1)


$tag(string) (Required) The name of the filter to hook the $function_to_add callback to.
$function_to_add(callable) (Required) The callback to be run when the filter is applied.
$priority(int) (Optional) Used to specify the order in which the functions associated with a particular action are executed. Lower numbers correspond with earlier execution, and functions with the same priority are executed in the order in which they were added to the action.Default value: 10
$accepted_args(int) (Optional) The number of arguments the function accepts.Default value: 1


The way Plugin hooks work is that at various times while WordPress is running, WordPress checks to see if any Plugins have registered functions to run at that time, and if so, the functions are run. These functions modify the default behavior of WordPress.

There are two kinds of hooks:

Filters give you the ability to change the value of a piece of data during the execution of WordPress. Callback functions for filters will be passed through a variable, modified, and then returned. They are meant to work in an isolated manner, and should never affect global variables or anything else outside of the function.

Actions, in contrast, allow you to add to or change how WordPress operates. Your callback function will run at a specific point in in the execution of WordPress, and can perform some kind of task, like echoing output to the user or inserting something into the database.

Filter Reference

Action Reference


Plugin API

Filters vs Actions

Got any WordPress Question?