(string)$tag The name of the filter to hook the $function_to_add callback to.

Erforderlich: Ja

(callable)$function_to_add The callback to be run when the filter is applied.

Erforderlich: Ja

(int)$priority Optional. Used to specify the order in which the functions associated with a particular action are executed. Default 10. 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.

Erforderlich: Nein

Standard: 10

(int)$accepted_args Optional. The number of arguments the function accepts. Default 1.

WordPress offers filter hooks to allow plugins to modify
various types of internal data at runtime.

A plugin can modify data by binding a callback to a filter hook. When the filter
is later applied, each bound callback is run in order of priority, and given
the opportunity to modify a value by returning a new value.

The following example shows how a callback function is bound to a filter hook.

Note that $example is passed to the callback, (maybe) modified, then returned:

Bound callbacks can accept from none to the total number of arguments passed as parameters
in the corresponding apply_filters() call.

In other words, if an apply_filters() call passes four total arguments, callbacks bound to
it can accept none (the same as 1) of the arguments or up to four. The important part is that
the $accepted_args value must reflect the number of arguments the bound callback actually
opted to accept. If no arguments were accepted by the callback that is considered to be the
same as accepting 1 argument. For example: