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 |
|---|---|
| 236 | * @param array $request { |
| 237 | * The array of request data. All arguments are optional and may be empty. |
| 238 | * |
| 239 | * @type string $app_name The suggested name of the application. |
| 240 | * @type string $success_url The url the user will be redirected to after approving the application. |
| 241 | * @type string $reject_url The url the user will be redirected to after rejecting the application. |
| 242 | * } |
| 243 | * @param WP_User $user The user authorizing the application. |
| 244 | */ |
| 245 | do_action( 'wp_authorize_application_password_form', $request, $user ); |
| 246 | ?> |
| 247 | |
| 248 | <?php |
| 249 | submit_button( |
| 250 | __( 'Yes, I approve of this connection.' ), |
| 251 | 'primary', |
| 252 | 'approve', |
| 253 | false, |
| 254 | array( |