wppaste
WordPress

do_action( 'wp_authorize_application_password_form', array $request, WP_User $user )

Since
5.6.0
Fires in the Authorize Application Password form before the submit buttons.

Compatibility

WordPress
since 5.6.0
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in every tracked release (6.7.7 to 7.1.0).

Parameters

$requestarray
{ The array of request data. All arguments are optional and may be empty.
@type string $app_name The suggested name of the application.
@type string $success_url The URL the user will be redirected to after approving the application.
@type string $reject_url The URL the user will be redirected to after rejecting the application.
}
  • $app_namestring

    The suggested name of the application.
  • $success_urlstring

    The URL the user will be redirected to after approving the application.
  • $reject_urlstring

    The URL the user will be redirected to after rejecting the application.
$userWP_User
The user authorizing the application.

Where this hook fires · 1

  • wp-admin/authorize-application.php:266file scope

Source code

				 *     @type string $app_name    The suggested name of the application.				 *     @type string $success_url The URL the user will be redirected to after approving the application.				 *     @type string $reject_url  The URL the user will be redirected to after rejecting the application.				 * }				 * @param WP_User $user The user authorizing the application.				 */				do_action( 'wp_authorize_application_password_form', $request, $user );				?> 				<?php				submit_button(					__( 'Yes, I approve of this connection' ),					'primary',

Changelog

Introduced in 5.6.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data
Generated from the wordpress-develop 7.1.0 tag, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.
Corrections
Something wrong on this page? Report it and it gets fixed in the next regeneration.