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.
$new_password, $request, $user
Sortie :
@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.
// Ajouter une fonction au hook action 'wp_authorize_application_password_form_approved_no_js'
add_action('wp_authorize_application_password_form_approved_no_js', 'ma_fonction_personnalisee', 10, 1);
function ma_fonction_personnalisee($new_password, $request, $user) {
// Votre code ici
error_log('Hook wp_authorize_application_password_form_approved_no_js déclenché');
}
Chargement des actualités...