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 |
---|---|
400 | setcookie( TEST_COOKIE, 'WP Cookie check', 0, COOKIEPATH, COOKIE_DOMAIN, $secure ); |
401 | if ( SITECOOKIEPATH != COOKIEPATH ) |
402 | setcookie( TEST_COOKIE, 'WP Cookie check', 0, SITECOOKIEPATH, COOKIE_DOMAIN, $secure ); |
403 |
|
404 | /** |
405 | * Fires when the login form is initialized. |
406 | * |
407 | * @since 3.2.0 |
408 | */ |
409 | do_action( 'login_init' ); |
410 | /** |
411 | * Fires before a specified login form action. |
412 | * |
413 | * The dynamic portion of the hook name, `$action`, refers to the action |
414 | * that brought the visitor to the login form. Actions include 'postpass', |
415 | * 'logout', 'lostpassword', etc. |
416 | * |
417 | * @since 2.8.0 |
418 | */ |