wp_authorize_application_password_form_approved_no_js
Fires in the Authorize Application Password new password section in the no-JS version.
In most cases, this should be used in combination with the {@see 'wp_application_passwords_approve_app_request_success'} action to ensure that both the JS and no-JS variants are handled.
Использование
add_action( 'wp_authorize_application_password_form_approved_no_js', 'wp_kama_authorize_application_password_form_approved_no_js_action', 10, 3 ); /** * Function for `wp_authorize_application_password_form_approved_no_js` action-hook. * * @param string $new_password The newly generated application password. * @param array $request The array of request data. All arguments are optional and may be empty. * @param WP_User $user The user authorizing the application. * * @return void */ function wp_kama_authorize_application_password_form_approved_no_js_action( $new_password, $request, $user ){ // action... }
- $new_password(строка)
- The newly generated application password.
- $request(массив)
- The array of request data. All arguments are optional and may be empty.
- $user(WP_User)
- The user authorizing the application.
Список изменений
С версии 5.6.0 | Введена. |
С версии 5.6.1 | Corrected action name and signature. |
Где вызывается хук
В файле: /wp-admin/authorize-application.php
wp_authorize_application_password_form_approved_no_js
wp-admin/authorize-application.php 236
do_action( 'wp_authorize_application_password_form_approved_no_js', $new_password, $request, $user );