WP hooks navigation: Home/browse • Actions index • Filters index
To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).
The best way to understand what a hook does is to look at where it occurs in the source code.
do_action( "hook_name" )
apply_filters( "hook_name", "what_to_filter" )
.Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.
Line | Code |
---|---|
384 | * |
385 | * The dynamic portion of the hook name, `$option`, refers to the user option name. |
386 | * |
387 | * @since 2.5.0 |
388 | * |
389 | * @param mixed $result Value for the user's option. |
390 | * @param string $option Name of the option being retrieved. |
391 | * @param WP_User $user WP_User object of the user whose option is being retrieved. |
392 | */ |
393 | return apply_filters( "get_user_option_{$option}", $result, $option, $user ); |
394 | } |
395 |
|
396 | /** |
397 | * Update user option with global blog capability. |
398 | * |
399 | * User options are just like user metadata except that they have support for |
400 | * global blog options. If the 'global' parameter is false, which it is by default |
401 | * it will prepend the WordPress table prefix to the option name. |
402 | * |