2004-08-01 05:13:50 -04:00
< ? php
2008-08-16 03:27:34 -04:00
/**
* Edit user administration panel .
*
* @ package WordPress
* @ subpackage Administration
*/
2008-01-31 16:44:17 -05:00
2008-08-16 03:27:34 -04:00
/** WordPress Administration Bootstrap */
2020-02-06 01:33:11 -05:00
require_once __DIR__ . '/admin.php' ;
2004-08-01 05:13:50 -04:00
2013-02-16 13:28:41 -05:00
wp_reset_vars ( array ( 'action' , 'user_id' , 'wp_http_referer' ) );
2010-04-02 02:46:07 -04:00
2017-11-30 18:11:00 -05:00
$user_id = ( int ) $user_id ;
2010-04-02 02:46:07 -04:00
$current_user = wp_get_current_user ();
2017-11-30 18:11:00 -05:00
if ( ! defined ( 'IS_PROFILE_PAGE' ) ) {
2010-04-02 02:46:07 -04:00
define ( 'IS_PROFILE_PAGE' , ( $user_id == $current_user -> ID ) );
2017-11-30 18:11:00 -05:00
}
2010-04-02 02:46:07 -04:00
2017-11-30 18:11:00 -05:00
if ( ! $user_id && IS_PROFILE_PAGE ) {
2010-04-02 02:46:07 -04:00
$user_id = $current_user -> ID ;
2017-11-30 18:11:00 -05:00
} elseif ( ! $user_id && ! IS_PROFILE_PAGE ) {
wp_die ( __ ( 'Invalid user ID.' ) );
} elseif ( ! get_userdata ( $user_id ) ) {
wp_die ( __ ( 'Invalid user ID.' ) );
}
2008-01-31 17:03:48 -05:00
2017-11-30 18:11:00 -05:00
wp_enqueue_script ( 'user-profile' );
2008-01-31 16:44:17 -05:00
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
if ( wp_is_application_passwords_available_for_user ( $user_id ) ) {
wp_enqueue_script ( 'application-passwords' );
}
2017-01-15 02:14:39 -05:00
if ( IS_PROFILE_PAGE ) {
$title = __ ( 'Profile' );
} else {
2019-09-02 20:41:05 -04:00
/* translators: %s: User's display name. */
2017-01-15 02:14:39 -05:00
$title = __ ( 'Edit User %s' );
}
2017-11-30 18:11:00 -05:00
if ( current_user_can ( 'edit_users' ) && ! IS_PROFILE_PAGE ) {
2008-01-31 17:03:48 -05:00
$submenu_file = 'users.php' ;
2017-11-30 18:11:00 -05:00
} else {
2008-01-31 17:03:48 -05:00
$submenu_file = 'profile.php' ;
2017-11-30 18:11:00 -05:00
}
2010-10-07 15:34:18 -04:00
2017-11-30 18:11:00 -05:00
if ( current_user_can ( 'edit_users' ) && ! is_user_admin () ) {
2010-10-07 15:34:18 -04:00
$parent_file = 'users.php' ;
2017-11-30 18:11:00 -05:00
} else {
2010-10-07 15:34:18 -04:00
$parent_file = 'profile.php' ;
2017-11-30 18:11:00 -05:00
}
2004-08-01 05:13:50 -04:00
2017-11-30 18:11:00 -05:00
$profile_help = '<p>' . __ ( 'Your profile contains information about you (your “account”) as well as some personal options related to using WordPress.' ) . '</p>' .
'<p>' . __ ( 'You can change your password, turn on keyboard shortcuts, change the color scheme of your WordPress administration screens, and turn off the WYSIWYG (Visual) editor, among other things. You can hide the Toolbar (formerly called the Admin Bar) from the front end of your site, however it cannot be disabled on the admin screens.' ) . '</p>' .
2016-10-21 06:41:51 -04:00
'<p>' . __ ( 'You can select the language you wish to use while using the WordPress administration screen without affecting the language site visitors see.' ) . '</p>' .
2017-11-30 18:11:00 -05:00
'<p>' . __ ( 'Your username cannot be changed, but you can use other fields to enter your real name or a nickname, and change which name to display on your posts.' ) . '</p>' .
2015-07-25 21:52:25 -04:00
'<p>' . __ ( 'You can log out of other devices, such as your phone or a public computer, by clicking the Log Out Everywhere Else button.' ) . '</p>' .
2017-11-30 18:11:00 -05:00
'<p>' . __ ( 'Required fields are indicated; the rest are optional. Profile information will only be displayed if your theme is set up to do so.' ) . '</p>' .
'<p>' . __ ( 'Remember to click the Update Profile button when you are finished.' ) . '</p>' ;
get_current_screen () -> add_help_tab (
array (
'id' => 'overview' ,
'title' => __ ( 'Overview' ),
'content' => $profile_help ,
)
);
2011-11-01 23:12:37 -04:00
2011-11-02 16:14:10 -04:00
get_current_screen () -> set_help_sidebar (
2017-11-30 18:11:00 -05:00
'<p><strong>' . __ ( 'For more information:' ) . '</strong></p>' .
2019-07-25 18:45:57 -04:00
'<p>' . __ ( '<a href="https://wordpress.org/support/article/users-your-profile-screen/">Documentation on User Profiles</a>' ) . '</p>' .
2019-04-08 18:59:56 -04:00
'<p>' . __ ( '<a href="https://wordpress.org/support/">Support</a>' ) . '</p>'
2010-05-27 19:10:26 -04:00
);
2016-02-24 16:43:25 -05:00
$wp_http_referer = remove_query_arg ( array ( 'update' , 'delete_count' , 'user_id' ), $wp_http_referer );
2006-06-08 14:36:05 -04:00
2011-03-31 02:33:20 -04:00
$user_can_edit = current_user_can ( 'edit_posts' ) || current_user_can ( 'edit_pages' );
2009-05-24 14:46:01 -04:00
2013-11-30 20:35:10 -05:00
/**
2016-05-22 14:01:30 -04:00
* Filters whether to allow administrators on Multisite to edit every user .
2013-11-30 20:35:10 -05:00
*
* Enabling the user editing form via this filter also hinges on the user holding
* the 'manage_network_users' cap , and the logged - in user not matching the user
* profile open for editing .
*
* The filter was introduced to replace the EDIT_ANY_USER constant .
*
* @ since 3.0 . 0
*
* @ param bool $allow Whether to allow editing of any user . Default true .
*/
if ( is_multisite ()
&& ! current_user_can ( 'manage_network_users' )
&& $user_id != $current_user -> ID
&& ! apply_filters ( 'enable_edit_any_user_configuration' , true )
) {
2016-06-29 11:16:29 -04:00
wp_die ( __ ( 'Sorry, you are not allowed to edit this user.' ) );
2013-11-30 20:35:10 -05:00
}
2010-01-15 17:11:12 -05:00
2010-02-02 13:00:45 -05:00
// Execute confirmed email change. See send_confirmation_on_profile_email().
2017-11-30 18:11:00 -05:00
if ( IS_PROFILE_PAGE && isset ( $_GET [ 'newuseremail' ] ) && $current_user -> ID ) {
2016-02-24 10:34:28 -05:00
$new_email = get_user_meta ( $current_user -> ID , '_new_email' , true );
2017-11-30 18:11:00 -05:00
if ( $new_email && hash_equals ( $new_email [ 'hash' ], $_GET [ 'newuseremail' ] ) ) {
$user = new stdClass ;
$user -> ID = $current_user -> ID ;
$user -> user_email = esc_html ( trim ( $new_email [ 'newemail' ] ) );
2017-07-26 22:10:42 -04:00
if ( is_multisite () && $wpdb -> get_var ( $wpdb -> prepare ( " SELECT user_login FROM { $wpdb -> signups } WHERE user_login = %s " , $current_user -> user_login ) ) ) {
2010-02-02 13:00:45 -05:00
$wpdb -> query ( $wpdb -> prepare ( " UPDATE { $wpdb -> signups } SET user_email = %s WHERE user_login = %s " , $user -> user_email , $current_user -> user_login ) );
2016-02-24 10:34:28 -05:00
}
2012-08-10 11:36:54 -04:00
wp_update_user ( $user );
2016-02-24 10:34:28 -05:00
delete_user_meta ( $current_user -> ID , '_new_email' );
wp_redirect ( add_query_arg ( array ( 'updated' => 'true' ), self_admin_url ( 'profile.php' ) ) );
2010-02-02 13:00:45 -05:00
die ();
2016-02-24 10:34:28 -05:00
} else {
wp_redirect ( add_query_arg ( array ( 'error' => 'new-email' ), self_admin_url ( 'profile.php' ) ) );
2010-02-02 13:00:45 -05:00
}
2017-07-26 22:10:42 -04:00
} elseif ( IS_PROFILE_PAGE && ! empty ( $_GET [ 'dismiss' ] ) && $current_user -> ID . '_new_email' === $_GET [ 'dismiss' ] ) {
2016-03-30 10:44:26 -04:00
check_admin_referer ( 'dismiss-' . $current_user -> ID . '_new_email' );
2016-02-24 10:34:28 -05:00
delete_user_meta ( $current_user -> ID , '_new_email' );
2017-11-30 18:11:00 -05:00
wp_redirect ( add_query_arg ( array ( 'updated' => 'true' ), self_admin_url ( 'profile.php' ) ) );
2010-05-22 03:53:59 -04:00
die ();
2010-02-02 13:00:45 -05:00
}
2017-11-30 18:11:00 -05:00
switch ( $action ) {
case 'update' :
check_admin_referer ( 'update-user_' . $user_id );
2006-03-05 17:45:44 -05:00
2017-11-30 18:11:00 -05:00
if ( ! current_user_can ( 'edit_user' , $user_id ) ) {
wp_die ( __ ( 'Sorry, you are not allowed to edit this user.' ) );
}
2006-09-24 06:08:58 -04:00
2017-11-30 18:11:00 -05:00
if ( IS_PROFILE_PAGE ) {
/**
Users: Change "Your Profile" and "My Profile" links in admin menu and toolbar to just "Profile" for consistency.
Props donmhico, bcworkz, seanchayes, mikeschroder, garrett-eclipse, akhileshsabharwal, ScottSmith, nacin, jenmylo, afercia, swissspidy, felix-edelmann, helen, melchoyce, karmatosed.
Fixes #26769.
Built from https://develop.svn.wordpress.org/trunk@47600
git-svn-id: http://core.svn.wordpress.org/trunk@47375 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-04-20 04:39:06 -04:00
* Fires before the page loads on the 'Profile' editing screen .
2017-11-30 18:11:00 -05:00
*
* The action only fires if the current user is editing their own profile .
*
* @ since 2.0 . 0
*
* @ param int $user_id The user ID .
*/
do_action ( 'personal_options_update' , $user_id );
} else {
/**
* Fires before the page loads on the 'Edit User' screen .
*
* @ since 2.7 . 0
*
* @ param int $user_id The user ID .
*/
do_action ( 'edit_user_profile_update' , $user_id );
}
2008-01-31 16:44:17 -05:00
2017-11-30 18:11:00 -05:00
// Update the email address in signups, if present.
if ( is_multisite () ) {
$user = get_userdata ( $user_id );
2010-01-26 12:51:50 -05:00
2017-11-30 18:11:00 -05:00
if ( $user -> user_login && isset ( $_POST [ 'email' ] ) && is_email ( $_POST [ 'email' ] ) && $wpdb -> get_var ( $wpdb -> prepare ( " SELECT user_login FROM { $wpdb -> signups } WHERE user_login = %s " , $user -> user_login ) ) ) {
$wpdb -> query ( $wpdb -> prepare ( " UPDATE { $wpdb -> signups } SET user_email = %s WHERE user_login = %s " , $_POST [ 'email' ], $user_login ) );
}
}
2015-02-22 20:34:24 -05:00
2017-11-30 18:11:00 -05:00
// Update the user.
$errors = edit_user ( $user_id );
2010-04-02 02:46:07 -04:00
2017-11-30 18:11:00 -05:00
// Grant or revoke super admin status if requested.
if ( is_multisite () && is_network_admin () && ! IS_PROFILE_PAGE && current_user_can ( 'manage_network_options' ) && ! isset ( $super_admins ) && empty ( $_POST [ 'super_admin' ] ) == is_super_admin ( $user_id ) ) {
empty ( $_POST [ 'super_admin' ] ) ? revoke_super_admin ( $user_id ) : grant_super_admin ( $user_id );
}
2005-07-12 11:53:13 -04:00
2017-11-30 18:11:00 -05:00
if ( ! is_wp_error ( $errors ) ) {
$redirect = add_query_arg ( 'updated' , true , get_edit_user_link ( $user_id ) );
if ( $wp_http_referer ) {
$redirect = add_query_arg ( 'wp_http_referer' , urlencode ( $wp_http_referer ), $redirect );
}
wp_redirect ( $redirect );
exit ;
}
2004-08-01 05:13:50 -04:00
2019-01-11 01:26:50 -05:00
// Intentional fall-through to display $errors.
2017-11-30 18:11:00 -05:00
default :
$profileuser = get_user_to_edit ( $user_id );
2004-08-01 05:13:50 -04:00
2017-11-30 18:11:00 -05:00
if ( ! current_user_can ( 'edit_user' , $user_id ) ) {
wp_die ( __ ( 'Sorry, you are not allowed to edit this user.' ) );
}
2006-09-24 06:08:58 -04:00
2017-11-30 18:11:00 -05:00
$title = sprintf ( $title , $profileuser -> display_name );
$sessions = WP_Session_Tokens :: get_instance ( $profileuser -> ID );
2014-11-13 10:21:21 -05:00
2020-02-06 01:33:11 -05:00
require_once ABSPATH . 'wp-admin/admin-header.php' ;
2018-08-16 21:51:36 -04:00
?>
2004-08-01 05:13:50 -04:00
2018-08-16 21:51:36 -04:00
< ? php if ( ! IS_PROFILE_PAGE && is_super_admin ( $profileuser -> ID ) && current_user_can ( 'manage_network_options' ) ) { ?>
2017-11-30 18:11:00 -05:00
< div class = " notice notice-info " >< p >< strong >< ? php _e ( 'Important:' ); ?> </strong> <?php _e( 'This user has super admin privileges.' ); ?></p></div>
2010-04-02 02:46:07 -04:00
< ? php } ?>
2018-08-16 21:51:36 -04:00
< ? php if ( isset ( $_GET [ 'updated' ] ) ) : ?>
2015-04-01 18:06:28 -04:00
< div id = " message " class = " updated notice is-dismissible " >
2018-08-16 21:51:36 -04:00
< ? php if ( IS_PROFILE_PAGE ) : ?>
2017-11-30 18:11:00 -05:00
< p >< strong >< ? php _e ( 'Profile updated.' ); ?> </strong></p>
< ? php else : ?>
< p >< strong >< ? php _e ( 'User updated.' ); ?> </strong></p>
2011-11-14 17:09:15 -05:00
< ? php endif ; ?>
2018-08-16 21:51:36 -04:00
< ? php if ( $wp_http_referer && false === strpos ( $wp_http_referer , 'user-new.php' ) && ! IS_PROFILE_PAGE ) : ?>
2020-11-09 05:53:10 -05:00
< p >< a href = " <?php echo esc_url( wp_validate_redirect( esc_url_raw( $wp_http_referer ), self_admin_url( 'users.php' ) ) ); ?> " >< ? php _e ( '← Go to Users' ); ?> </a></p>
2006-06-08 14:36:05 -04:00
< ? php endif ; ?>
2004-08-01 05:13:50 -04:00
</ div >
2018-08-16 21:51:36 -04:00
< ? php endif ; ?>
< ? php if ( isset ( $_GET [ 'error' ] ) ) : ?>
2016-02-24 10:34:28 -05:00
< div class = " notice notice-error " >
2020-05-16 14:42:12 -04:00
< ? php if ( 'new-email' === $_GET [ 'error' ] ) : ?>
2016-02-24 10:34:28 -05:00
< p >< ? php _e ( 'Error while saving the new email address. Please try again.' ); ?> </p>
< ? php endif ; ?>
</ div >
2018-08-16 21:51:36 -04:00
< ? php endif ; ?>
< ? php if ( isset ( $errors ) && is_wp_error ( $errors ) ) : ?>
2010-04-27 17:57:18 -04:00
< div class = " error " >< p >< ? php echo implode ( " </p> \n <p> " , $errors -> get_error_messages () ); ?> </p></div>
2018-08-16 21:51:36 -04:00
< ? php endif ; ?>
2004-08-01 05:13:50 -04:00
2008-03-10 18:09:26 -04:00
< div class = " wrap " id = " profile-page " >
2017-11-30 18:11:00 -05:00
< h1 class = " wp-heading-inline " >
2018-08-16 21:51:36 -04:00
< ? php
echo esc_html ( $title );
?>
2017-11-30 18:11:00 -05:00
</ h1 >
2016-12-07 17:08:43 -05:00
2018-08-16 21:51:36 -04:00
< ? php
if ( ! IS_PROFILE_PAGE ) {
if ( current_user_can ( 'create_users' ) ) {
?>
2015-07-03 12:42:24 -04:00
< a href = " user-new.php " class = " page-title-action " >< ? php echo esc_html_x ( 'Add New' , 'user' ); ?> </a>
2011-05-19 15:52:11 -04:00
< ? php } elseif ( is_multisite () && current_user_can ( 'promote_users' ) ) { ?>
2015-07-03 12:42:24 -04:00
< a href = " user-new.php " class = " page-title-action " >< ? php echo esc_html_x ( 'Add Existing' , 'user' ); ?> </a>
2018-08-16 21:51:36 -04:00
< ? php
2019-01-12 01:41:52 -05:00
}
2018-08-16 21:51:36 -04:00
}
?>
2016-12-07 17:08:43 -05:00
< hr class = " wp-header-end " >
2017-11-30 18:11:00 -05:00
< form id = " your-profile " action = " <?php echo esc_url( self_admin_url( IS_PROFILE_PAGE ? 'profile.php' : 'user-edit.php' ) ); ?> " method = " post " novalidate = " novalidate "
2020-01-28 19:45:18 -05:00
< ? php
/**
* Fires inside the your - profile form tag on the user editing screen .
*
* @ since 3.0 . 0
*/
do_action ( 'user_edit_form_tag' );
?>
2017-11-30 18:11:00 -05:00
>
2018-08-16 21:51:36 -04:00
< ? php wp_nonce_field ( 'update-user_' . $user_id ); ?>
< ? php if ( $wp_http_referer ) : ?>
2017-11-30 18:11:00 -05:00
< input type = " hidden " name = " wp_http_referer " value = " <?php echo esc_url( $wp_http_referer ); ?> " />
2018-08-16 21:51:36 -04:00
< ? php endif ; ?>
2005-09-13 20:03:02 -04:00
< p >
< input type = " hidden " name = " from " value = " profile " />
2014-02-02 05:04:13 -05:00
< input type = " hidden " name = " checkuser_id " value = " <?php echo get_current_user_id(); ?> " />
2005-09-13 20:03:02 -04:00
</ p >
2015-09-05 14:30:24 -04:00
< h2 >< ? php _e ( 'Personal Options' ); ?> </h2>
2008-01-31 16:44:17 -05:00
2019-05-24 17:56:54 -04:00
< table class = " form-table " role = " presentation " >
2018-08-16 21:51:36 -04:00
< ? php if ( ! ( IS_PROFILE_PAGE && ! $user_can_edit ) ) : ?>
2014-10-01 20:56:16 -04:00
< tr class = " user-rich-editing-wrap " >
2015-01-25 13:33:22 -05:00
< th scope = " row " >< ? php _e ( 'Visual Editor' ); ?> </th>
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
< td >
< label for = " rich_editing " >< input name = " rich_editing " type = " checkbox " id = " rich_editing " value = " false " < ? php checked ( 'false' , $profileuser -> rich_editing ); ?> />
< ? php _e ( 'Disable the visual editor when writing' ); ?>
</ label >
</ td >
2008-03-10 18:09:26 -04:00
</ tr >
2018-08-16 21:51:36 -04:00
< ? php endif ; ?>
< ? php
$show_syntax_highlighting_preference = (
// For Custom HTML widget and Additional CSS in Customizer.
user_can ( $profileuser , 'edit_theme_options' )
||
// Edit plugins.
user_can ( $profileuser , 'edit_plugins' )
||
// Edit themes.
user_can ( $profileuser , 'edit_themes' )
);
?>
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
2018-08-16 21:51:36 -04:00
< ? php if ( $show_syntax_highlighting_preference ) : ?>
Editor: Add CodeMirror-powered code editor with syntax highlighting, linting, and auto-completion.
* Code editor is integrated into the Theme/Plugin Editor, Additional CSS in Customizer, and Custom HTML widget. Code editor is not yet integrated into the post editor, and it may not be until accessibility concerns are addressed.
* The CodeMirror component in the Custom HTML widget is integrated in a similar way to TinyMCE being integrated into the Text widget, adopting the same approach for integrating dynamic JavaScript-initialized fields.
* Linting is performed for JS, CSS, HTML, and JSON via JSHint, CSSLint, HTMLHint, and JSONLint respectively. Linting is not yet supported for PHP.
* When user lacks `unfiltered_html` the capability, the Custom HTML widget will report any Kses-invalid elements and attributes as errors via a custom Kses rule for HTMLHint.
* When linting errors are detected, the user will be prevented from saving the code until the errors are fixed, reducing instances of broken websites.
* The placeholder value is removed from Custom CSS in favor of a fleshed-out section description which now auto-expands when the CSS field is empty. See #39892.
* The CodeMirror library is included as `wp.CodeMirror` to prevent conflicts with any existing `CodeMirror` global.
* An `wp.codeEditor.initialize()` API in JS is provided to convert a `textarea` into CodeMirror, with a `wp_enqueue_code_editor()` function in PHP to manage enqueueing the assets and settings needed to edit a given type of code.
* A user preference is added to manage whether or not "syntax highlighting" is enabled. The feature is opt-out, being enabled by default.
* Allowed file extensions in the theme and plugin editors have been updated to include formats which CodeMirror has modes for: `conf`, `css`, `diff`, `patch`, `html`, `htm`, `http`, `js`, `json`, `jsx`, `less`, `md`, `php`, `phtml`, `php3`, `php4`, `php5`, `php7`, `phps`, `scss`, `sass`, `sh`, `bash`, `sql`, `svg`, `xml`, `yml`, `yaml`, `txt`.
Props westonruter, georgestephanis, obenland, melchoyce, pixolin, mizejewski, michelleweber, afercia, grahamarmfield, samikeijonen, rianrietveld, iseulde.
See #38707.
Fixes #12423, #39892.
Built from https://develop.svn.wordpress.org/trunk@41376
git-svn-id: http://core.svn.wordpress.org/trunk@41209 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2017-09-13 02:08:47 -04:00
< tr class = " user-syntax-highlighting-wrap " >
< th scope = " row " >< ? php _e ( 'Syntax Highlighting' ); ?> </th>
< td >
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
< label for = " syntax_highlighting " >< input name = " syntax_highlighting " type = " checkbox " id = " syntax_highlighting " value = " false " < ? php checked ( 'false' , $profileuser -> syntax_highlighting ); ?> />
< ? php _e ( 'Disable syntax highlighting when editing code' ); ?>
</ label >
Editor: Add CodeMirror-powered code editor with syntax highlighting, linting, and auto-completion.
* Code editor is integrated into the Theme/Plugin Editor, Additional CSS in Customizer, and Custom HTML widget. Code editor is not yet integrated into the post editor, and it may not be until accessibility concerns are addressed.
* The CodeMirror component in the Custom HTML widget is integrated in a similar way to TinyMCE being integrated into the Text widget, adopting the same approach for integrating dynamic JavaScript-initialized fields.
* Linting is performed for JS, CSS, HTML, and JSON via JSHint, CSSLint, HTMLHint, and JSONLint respectively. Linting is not yet supported for PHP.
* When user lacks `unfiltered_html` the capability, the Custom HTML widget will report any Kses-invalid elements and attributes as errors via a custom Kses rule for HTMLHint.
* When linting errors are detected, the user will be prevented from saving the code until the errors are fixed, reducing instances of broken websites.
* The placeholder value is removed from Custom CSS in favor of a fleshed-out section description which now auto-expands when the CSS field is empty. See #39892.
* The CodeMirror library is included as `wp.CodeMirror` to prevent conflicts with any existing `CodeMirror` global.
* An `wp.codeEditor.initialize()` API in JS is provided to convert a `textarea` into CodeMirror, with a `wp_enqueue_code_editor()` function in PHP to manage enqueueing the assets and settings needed to edit a given type of code.
* A user preference is added to manage whether or not "syntax highlighting" is enabled. The feature is opt-out, being enabled by default.
* Allowed file extensions in the theme and plugin editors have been updated to include formats which CodeMirror has modes for: `conf`, `css`, `diff`, `patch`, `html`, `htm`, `http`, `js`, `json`, `jsx`, `less`, `md`, `php`, `phtml`, `php3`, `php4`, `php5`, `php7`, `phps`, `scss`, `sass`, `sh`, `bash`, `sql`, `svg`, `xml`, `yml`, `yaml`, `txt`.
Props westonruter, georgestephanis, obenland, melchoyce, pixolin, mizejewski, michelleweber, afercia, grahamarmfield, samikeijonen, rianrietveld, iseulde.
See #38707.
Fixes #12423, #39892.
Built from https://develop.svn.wordpress.org/trunk@41376
git-svn-id: http://core.svn.wordpress.org/trunk@41209 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2017-09-13 02:08:47 -04:00
</ td >
</ tr >
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
< ? php endif ; ?>
2018-08-16 21:51:36 -04:00
< ? php if ( count ( $_wp_admin_css_colors ) > 1 && has_action ( 'admin_color_scheme_picker' ) ) : ?>
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
< tr class = " user-admin-color-wrap " >
< th scope = " row " >< ? php _e ( 'Admin Color Scheme' ); ?> </th>
< td >
2018-08-16 21:51:36 -04:00
< ? php
/**
* Fires in the 'Admin Color Scheme' section of the user editing screen .
*
* The section is only enabled if a callback is hooked to the action ,
* and if there is more than one defined color scheme for the admin .
*
* @ since 3.0 . 0
* @ since 3.8 . 1 Added `$user_id` parameter .
*
* @ param int $user_id The user ID .
*/
do_action ( 'admin_color_scheme_picker' , $user_id );
?>
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
</ td >
</ tr >
2020-01-28 19:45:18 -05:00
< ? php endif ; // End if count ( $_wp_admin_css_colors ) > 1 ?>
< ? php if ( ! ( IS_PROFILE_PAGE && ! $user_can_edit ) ) : ?>
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
< tr class = " user-comment-shortcuts-wrap " >
< th scope = " row " >< ? php _e ( 'Keyboard Shortcuts' ); ?> </th>
< td >
< label for = " comment_shortcuts " >
< input type = " checkbox " name = " comment_shortcuts " id = " comment_shortcuts " value = " true " < ? php checked ( 'true' , $profileuser -> comment_shortcuts ); ?> />
< ? php _e ( 'Enable keyboard shortcuts for comment moderation.' ); ?>
</ label >
< ? php _e ( '<a href="https://wordpress.org/support/article/keyboard-shortcuts/" target="_blank">More information</a>' ); ?>
</ td >
</ tr >
2019-01-12 01:41:52 -05:00
< ? php endif ; ?>
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
< tr class = " show-admin-bar user-admin-bar-front-wrap " >
< th scope = " row " >< ? php _e ( 'Toolbar' ); ?> </th>
< td >
< label for = " admin_bar_front " >
< input name = " admin_bar_front " type = " checkbox " id = " admin_bar_front " value = " 1 " < ? php checked ( _get_admin_bar_pref ( 'front' , $profileuser -> ID ) ); ?> />
< ? php _e ( 'Show Toolbar when viewing site' ); ?>
</ label >< br />
</ td >
</ tr >
2016-10-03 03:04:29 -04:00
2018-08-16 21:51:36 -04:00
< ? php
$languages = get_available_languages ();
if ( $languages ) :
?>
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
< tr class = " user-language-wrap " >
< th scope = " row " >
2019-09-02 20:41:05 -04:00
< ? php /* translators: The user language selection field label. */ ?>
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
< label for = " locale " >< ? php _e ( 'Language' ); ?> <span class="dashicons dashicons-translation" aria-hidden="true"></span></label>
</ th >
< td >
2018-08-16 21:51:36 -04:00
< ? php
$user_locale = $profileuser -> locale ;
2016-10-03 03:04:29 -04:00
2018-08-16 21:51:36 -04:00
if ( 'en_US' === $user_locale ) {
$user_locale = '' ;
} elseif ( '' === $user_locale || ! in_array ( $user_locale , $languages , true ) ) {
$user_locale = 'site-default' ;
}
2016-10-03 03:04:29 -04:00
2018-08-16 21:51:36 -04:00
wp_dropdown_languages (
array (
'name' => 'locale' ,
'id' => 'locale' ,
'selected' => $user_locale ,
'languages' => $languages ,
'show_available_translations' => false ,
'show_option_site_default' => true ,
)
);
?>
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
</ td >
</ tr >
2018-08-16 21:51:36 -04:00
< ? php
2016-10-03 03:04:29 -04:00
endif ;
2018-08-16 21:51:36 -04:00
?>
2016-10-03 03:04:29 -04:00
2018-08-16 21:51:36 -04:00
< ? php
/**
* Fires at the end of the 'Personal Options' settings table on the user editing screen .
*
* @ since 2.7 . 0
*
* @ param WP_User $profileuser The current WP_User object .
*/
do_action ( 'personal_options' , $profileuser );
?>
2014-11-13 10:21:21 -05:00
2008-03-11 17:06:03 -04:00
</ table >
2018-08-16 21:51:36 -04:00
< ? php
if ( IS_PROFILE_PAGE ) {
/**
Users: Change "Your Profile" and "My Profile" links in admin menu and toolbar to just "Profile" for consistency.
Props donmhico, bcworkz, seanchayes, mikeschroder, garrett-eclipse, akhileshsabharwal, ScottSmith, nacin, jenmylo, afercia, swissspidy, felix-edelmann, helen, melchoyce, karmatosed.
Fixes #26769.
Built from https://develop.svn.wordpress.org/trunk@47600
git-svn-id: http://core.svn.wordpress.org/trunk@47375 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-04-20 04:39:06 -04:00
* Fires after the 'Personal Options' settings table on the 'Profile' editing screen .
2018-08-16 21:51:36 -04:00
*
* The action only fires if the current user is editing their own profile .
*
* @ since 2.0 . 0
*
* @ param WP_User $profileuser The current WP_User object .
*/
do_action ( 'profile_personal_options' , $profileuser );
}
?>
2007-03-28 12:10:48 -04:00
2015-09-05 14:30:24 -04:00
< h2 >< ? php _e ( 'Name' ); ?> </h2>
2007-03-28 12:10:48 -04:00
2019-05-24 17:56:54 -04:00
< table class = " form-table " role = " presentation " >
2014-10-01 20:56:16 -04:00
< tr class = " user-user-login-wrap " >
2017-11-30 18:11:00 -05:00
< th >< label for = " user_login " >< ? php _e ( 'Username' ); ?> </label></th>
< td >< input type = " text " name = " user_login " id = " user_login " value = " <?php echo esc_attr( $profileuser->user_login ); ?> " disabled = " disabled " class = " regular-text " /> < span class = " description " >< ? php _e ( 'Usernames cannot be changed.' ); ?> </span></td>
2008-03-10 18:09:26 -04:00
</ tr >
2005-11-05 22:58:52 -05:00
2018-08-16 21:51:36 -04:00
< ? php if ( ! IS_PROFILE_PAGE && ! is_network_admin () && current_user_can ( 'promote_user' , $profileuser -> ID ) ) : ?>
2017-11-30 18:11:00 -05:00
< tr class = " user-role-wrap " >< th >< label for = " role " >< ? php _e ( 'Role' ); ?> </label></th>
2009-01-06 12:23:11 -05:00
< td >< select name = " role " id = " role " >
2018-08-16 21:51:36 -04:00
< ? php
2020-01-28 19:45:18 -05:00
// Compare user role against currently editable roles.
2018-08-16 21:51:36 -04:00
$user_roles = array_intersect ( array_values ( $profileuser -> roles ), array_keys ( get_editable_roles () ) );
$user_role = reset ( $user_roles );
2020-01-28 19:45:18 -05:00
// Print the full list of roles with the primary one selected.
2018-08-16 21:51:36 -04:00
wp_dropdown_roles ( $user_role );
2020-01-28 19:45:18 -05:00
// Print the 'no role' option. Make it selected if the user has no role yet.
2018-08-16 21:51:36 -04:00
if ( $user_role ) {
echo '<option value="">' . __ ( '— No role for this site —' ) . '</option>' ;
} else {
echo '<option value="" selected="selected">' . __ ( '— No role for this site —' ) . '</option>' ;
}
?>
2011-10-12 15:47:00 -04:00
</ select ></ td ></ tr >
2018-08-16 21:51:36 -04:00
< ? php
2020-01-28 19:45:18 -05:00
endif ; // End if ! IS_PROFILE_PAGE.
2010-12-07 13:10:16 -05:00
2019-01-12 01:41:52 -05:00
if ( is_multisite () && is_network_admin () && ! IS_PROFILE_PAGE && current_user_can ( 'manage_network_options' ) && ! isset ( $super_admins ) ) {
?>
2017-11-30 18:11:00 -05:00
< tr class = " user-super-admin-wrap " >< th >< ? php _e ( 'Super Admin' ); ?> </th>
2010-11-05 13:26:32 -04:00
< td >
2019-07-28 13:42:55 -04:00
< ? php if ( 0 !== strcasecmp ( $profileuser -> user_email , get_site_option ( 'admin_email' ) ) || ! is_super_admin ( $profileuser -> ID ) ) : ?>
2010-12-07 13:10:16 -05:00
< p >< label >< input type = " checkbox " id = " super_admin " name = " super_admin " < ? php checked ( is_super_admin ( $profileuser -> ID ) ); ?> /> <?php _e( 'Grant this user super admin privileges for the Network.' ); ?></label></p>
< ? php else : ?>
< p >< ? php _e ( 'Super admin privileges cannot be removed because this user has the network admin email.' ); ?> </p>
< ? php endif ; ?>
2010-04-02 02:46:07 -04:00
</ td ></ tr >
2019-01-12 01:41:52 -05:00
< ? php } ?>
2005-09-13 20:03:02 -04:00
2014-10-01 20:56:16 -04:00
< tr class = " user-first-name-wrap " >
2017-11-30 18:11:00 -05:00
< th >< label for = " first_name " >< ? php _e ( 'First Name' ); ?> </label></th>
< td >< input type = " text " name = " first_name " id = " first_name " value = " <?php echo esc_attr( $profileuser->first_name ); ?> " class = " regular-text " /></ td >
2008-03-10 18:09:26 -04:00
</ tr >
2014-10-01 20:56:16 -04:00
< tr class = " user-last-name-wrap " >
2017-11-30 18:11:00 -05:00
< th >< label for = " last_name " >< ? php _e ( 'Last Name' ); ?> </label></th>
< td >< input type = " text " name = " last_name " id = " last_name " value = " <?php echo esc_attr( $profileuser->last_name ); ?> " class = " regular-text " /></ td >
2008-03-10 18:09:26 -04:00
</ tr >
2014-10-01 20:56:16 -04:00
< tr class = " user-nickname-wrap " >
2017-11-30 18:11:00 -05:00
< th >< label for = " nickname " >< ? php _e ( 'Nickname' ); ?> <span class="description"><?php _e( '(required)' ); ?></span></label></th>
< td >< input type = " text " name = " nickname " id = " nickname " value = " <?php echo esc_attr( $profileuser->nickname ); ?> " class = " regular-text " /></ td >
2008-03-10 18:09:26 -04:00
</ tr >
2014-10-01 20:56:16 -04:00
< tr class = " user-display-name-wrap " >
2017-11-30 18:11:00 -05:00
< th >< label for = " display_name " >< ? php _e ( 'Display name publicly as' ); ?> </label></th>
2008-03-10 18:09:26 -04:00
< td >
2008-03-11 04:54:08 -04:00
< select name = " display_name " id = " display_name " >
2008-03-10 18:09:26 -04:00
< ? php
2017-11-30 18:11:00 -05:00
$public_display = array ();
$public_display [ 'display_nickname' ] = $profileuser -> nickname ;
$public_display [ 'display_username' ] = $profileuser -> user_login ;
2011-04-01 16:40:16 -04:00
2017-11-30 18:11:00 -05:00
if ( ! empty ( $profileuser -> first_name ) ) {
$public_display [ 'display_firstname' ] = $profileuser -> first_name ;
}
2011-04-01 16:40:16 -04:00
2017-11-30 18:11:00 -05:00
if ( ! empty ( $profileuser -> last_name ) ) {
$public_display [ 'display_lastname' ] = $profileuser -> last_name ;
}
2011-04-01 16:40:16 -04:00
2017-11-30 18:11:00 -05:00
if ( ! empty ( $profileuser -> first_name ) && ! empty ( $profileuser -> last_name ) ) {
$public_display [ 'display_firstlast' ] = $profileuser -> first_name . ' ' . $profileuser -> last_name ;
$public_display [ 'display_lastfirst' ] = $profileuser -> last_name . ' ' . $profileuser -> first_name ;
}
2011-04-01 16:40:16 -04:00
2020-04-04 23:02:11 -04:00
if ( ! in_array ( $profileuser -> display_name , $public_display , true ) ) { // Only add this if it isn't duplicated elsewhere.
2017-11-30 18:11:00 -05:00
$public_display = array ( 'display_displayname' => $profileuser -> display_name ) + $public_display ;
}
2011-04-01 16:40:16 -04:00
2009-04-23 01:55:26 -04:00
$public_display = array_map ( 'trim' , $public_display );
2010-03-01 17:34:43 -05:00
$public_display = array_unique ( $public_display );
2011-04-01 16:40:16 -04:00
2017-11-30 18:11:00 -05:00
foreach ( $public_display as $id => $item ) {
2018-08-16 21:51:36 -04:00
?>
2017-11-30 18:11:00 -05:00
< option < ? php selected ( $profileuser -> display_name , $item ); ?> ><?php echo $item; ?></option>
2018-08-16 21:51:36 -04:00
< ? php
2017-11-30 18:11:00 -05:00
}
2008-03-10 18:09:26 -04:00
?>
</ select >
2017-11-30 18:11:00 -05:00
</ td >
</ tr >
</ table >
2008-03-10 18:09:26 -04:00
2017-11-30 18:11:00 -05:00
< h2 >< ? php _e ( 'Contact Info' ); ?> </h2>
2008-03-10 18:09:26 -04:00
2019-05-24 17:56:54 -04:00
< table class = " form-table " role = " presentation " >
2017-11-30 18:11:00 -05:00
< tr class = " user-email-wrap " >
< th >< label for = " email " >< ? php _e ( 'Email' ); ?> <span class="description"><?php _e( '(required)' ); ?></span></label></th>
2018-02-11 07:23:31 -05:00
< td >< input type = " email " name = " email " id = " email " aria - describedby = " email-description " value = " <?php echo esc_attr( $profileuser->user_email ); ?> " class = " regular-text ltr " />
2017-11-30 18:11:00 -05:00
< ? php
2018-02-11 07:23:31 -05:00
if ( $profileuser -> ID == $current_user -> ID ) :
2018-08-16 21:51:36 -04:00
?>
2018-02-11 07:23:31 -05:00
< p class = " description " id = " email-description " >
2020-01-30 19:28:04 -05:00
< ? php _e ( 'If you change this, we will send you an email at your new address to confirm it. <strong>The new address will not become active until confirmed.</strong>' ); ?>
2018-02-11 07:23:31 -05:00
</ p >
2018-08-16 21:51:36 -04:00
< ? php
2018-02-11 07:23:31 -05:00
endif ;
2017-11-30 18:11:00 -05:00
$new_email = get_user_meta ( $current_user -> ID , '_new_email' , true );
if ( $new_email && $new_email [ 'newemail' ] != $current_user -> user_email && $profileuser -> ID == $current_user -> ID ) :
2018-08-16 21:51:36 -04:00
?>
2017-11-30 18:11:00 -05:00
< div class = " updated inline " >
< p >
2018-08-16 21:51:36 -04:00
< ? php
printf (
2019-09-02 20:41:05 -04:00
/* translators: %s: New email. */
2018-08-16 21:51:36 -04:00
__ ( 'There is a pending change of your email to %s.' ),
'<code>' . esc_html ( $new_email [ 'newemail' ] ) . '</code>'
);
printf (
' <a href="%1$s">%2$s</a>' ,
esc_url ( wp_nonce_url ( self_admin_url ( 'profile.php?dismiss=' . $current_user -> ID . '_new_email' ), 'dismiss-' . $current_user -> ID . '_new_email' ) ),
__ ( 'Cancel' )
);
?>
2017-11-30 18:11:00 -05:00
</ p >
</ div >
< ? php endif ; ?>
2010-05-22 03:53:59 -04:00
</ td >
2017-11-30 18:11:00 -05:00
</ tr >
2008-03-10 18:09:26 -04:00
2017-11-30 18:11:00 -05:00
< tr class = " user-url-wrap " >
< th >< label for = " url " >< ? php _e ( 'Website' ); ?> </label></th>
< td >< input type = " url " name = " url " id = " url " value = " <?php echo esc_attr( $profileuser->user_url ); ?> " class = " regular-text code " /></ td >
</ tr >
2008-03-10 18:09:26 -04:00
2018-08-16 21:51:36 -04:00
< ? php
foreach ( wp_get_user_contact_methods ( $profileuser ) as $name => $desc ) {
?>
2017-11-30 18:11:00 -05:00
< tr class = " user-<?php echo $name ; ?>-wrap " >
< th >< label for = " <?php echo $name ; ?> " >
2018-08-16 21:51:36 -04:00
< ? php
/**
* Filters a user contactmethod label .
*
* The dynamic portion of the filter hook , `$name` , refers to
* each of the keys in the contactmethods array .
*
* @ since 2.9 . 0
*
* @ param string $desc The translatable label for the contactmethod .
*/
echo apply_filters ( " user_ { $name } _label " , $desc );
?>
2014-11-30 06:42:24 -05:00
</ label ></ th >
2017-11-30 18:11:00 -05:00
< td >< input type = " text " name = " <?php echo $name ; ?> " id = " <?php echo $name ; ?> " value = " <?php echo esc_attr( $profileuser -> $name ); ?> " class = " regular-text " /></ td >
</ tr >
2018-08-16 21:51:36 -04:00
< ? php
}
?>
2017-11-30 18:11:00 -05:00
</ table >
2008-03-10 18:09:26 -04:00
2017-11-30 18:11:00 -05:00
< h2 >< ? php IS_PROFILE_PAGE ? _e ( 'About Yourself' ) : _e ( 'About the user' ); ?> </h2>
2008-03-10 18:09:26 -04:00
2019-05-24 17:56:54 -04:00
< table class = " form-table " role = " presentation " >
2014-10-01 20:56:16 -04:00
< tr class = " user-description-wrap " >
2017-11-30 18:11:00 -05:00
< th >< label for = " description " >< ? php _e ( 'Biographical Info' ); ?> </label></th>
2014-10-02 15:40:16 -04:00
< td >< textarea name = " description " id = " description " rows = " 5 " cols = " 30 " >< ? php echo $profileuser -> description ; // textarea_escaped ?></textarea>
2017-11-30 18:11:00 -05:00
< p class = " description " >< ? php _e ( 'Share a little biographical information to fill out your profile. This may be shown publicly.' ); ?> </p></td>
2008-03-10 18:09:26 -04:00
</ tr >
2005-09-13 20:03:02 -04:00
2018-08-16 21:51:36 -04:00
< ? php if ( get_option ( 'show_avatars' ) ) : ?>
2015-11-11 14:28:28 -05:00
< tr class = " user-profile-picture " >
< th >< ? php _e ( 'Profile Picture' ); ?> </th>
< td >
2018-08-16 21:51:36 -04:00
< ? php echo get_avatar ( $user_id ); ?>
2017-11-30 18:11:00 -05:00
< p class = " description " >
2018-08-16 21:51:36 -04:00
< ? php
if ( IS_PROFILE_PAGE ) {
$description = sprintf (
2019-09-02 20:41:05 -04:00
/* translators: %s: Gravatar URL. */
2019-05-25 11:19:53 -04:00
__ ( '<a href="%s">You can change your profile picture on Gravatar</a>.' ),
2018-08-16 21:51:36 -04:00
__ ( 'https://en.gravatar.com/' )
);
} else {
$description = '' ;
}
2015-11-11 14:28:28 -05:00
/**
2016-05-22 14:01:30 -04:00
* Filters the user profile picture description displayed under the Gravatar .
2015-11-11 14:28:28 -05:00
*
* @ since 4.4 . 0
2016-08-31 17:13:32 -04:00
* @ since 4.7 . 0 Added the `$profileuser` parameter .
2015-11-11 14:28:28 -05:00
*
2016-08-31 17:13:32 -04:00
* @ param string $description The description that will be printed .
* @ param WP_User $profileuser The current WP_User object .
2015-11-11 14:28:28 -05:00
*/
2016-08-31 17:13:32 -04:00
echo apply_filters ( 'user_profile_picture_description' , $description , $profileuser );
2018-08-16 21:51:36 -04:00
?>
2017-11-30 18:11:00 -05:00
</ p >
2015-11-11 14:28:28 -05:00
</ td >
</ tr >
2015-11-11 14:41:25 -05:00
< ? php endif ; ?>
2015-11-11 14:28:28 -05:00
2018-08-16 21:51:36 -04:00
< ? php
/**
* Filters the display of the password fields .
*
* @ since 1.5 . 1
* @ since 2.8 . 0 Added the `$profileuser` parameter .
* @ since 4.4 . 0 Now evaluated only in user - edit . php .
*
* @ param bool $show Whether to show the password fields . Default true .
* @ param WP_User $profileuser User object for the current user to edit .
*/
2019-07-01 08:52:01 -04:00
$show_password_fields = apply_filters ( 'show_password_fields' , true , $profileuser );
if ( $show_password_fields ) :
2018-08-16 21:51:36 -04:00
?>
2017-11-30 18:11:00 -05:00
</ table >
2015-07-22 16:45:27 -04:00
2017-11-30 18:11:00 -05:00
< h2 >< ? php _e ( 'Account Management' ); ?> </h2>
2019-05-24 17:56:54 -04:00
< table class = " form-table " role = " presentation " >
2014-10-01 20:56:16 -04:00
< tr id = " password " class = " user-pass1-wrap " >
2013-11-18 16:31:09 -05:00
< th >< label for = " pass1 " >< ? php _e ( 'New Password' ); ?> </label></th>
2013-07-03 17:23:55 -04:00
< td >
2013-07-03 17:24:02 -04:00
< input class = " hidden " value = " " /><!-- #24364 workaround -->
2020-10-20 14:27:13 -04:00
< button type = " button " class = " button wp-generate-pw hide-if-no-js " aria - expanded = " false " >< ? php _e ( 'Set New Password' ); ?> </button>
2015-07-01 10:48:24 -04:00
< div class = " wp-pwd hide-if-js " >
2015-07-27 17:25:25 -04:00
< span class = " password-input-wrapper " >
< input type = " password " name = " pass1 " id = " pass1 " class = " regular-text " value = " " autocomplete = " off " data - pw = " <?php echo esc_attr( wp_generate_password( 24 ) ); ?> " aria - describedby = " pass-strength-result " />
</ span >
2016-09-28 15:54:28 -04:00
< button type = " button " class = " button wp-hide-pw hide-if-no-js " data - toggle = " 0 " aria - label = " <?php esc_attr_e( 'Hide password' ); ?> " >
2019-03-13 19:37:57 -04:00
< span class = " dashicons dashicons-hidden " aria - hidden = " true " ></ span >
2015-07-13 18:35:24 -04:00
< span class = " text " >< ? php _e ( 'Hide' ); ?> </span>
2015-07-01 10:48:24 -04:00
</ button >
2020-10-29 14:43:06 -04:00
< button type = " button " class = " button wp-cancel-pw hide-if-no-js " data - toggle = " 0 " aria - label = " <?php esc_attr_e( 'Cancel password change' ); ?> " >
2019-03-13 19:37:57 -04:00
< span class = " dashicons dashicons-no " aria - hidden = " true " ></ span >
2015-07-22 14:36:24 -04:00
< span class = " text " >< ? php _e ( 'Cancel' ); ?> </span>
</ button >
2015-07-21 20:15:25 -04:00
< div style = " display:none " id = " pass-strength-result " aria - live = " polite " ></ div >
2015-07-01 10:48:24 -04:00
</ div >
2013-06-30 07:13:34 -04:00
</ td >
</ tr >
2015-07-01 10:48:24 -04:00
< tr class = " user-pass2-wrap hide-if-js " >
2013-11-18 16:31:09 -05:00
< th scope = " row " >< label for = " pass2 " >< ? php _e ( 'Repeat New Password' ); ?> </label></th>
2013-06-30 07:13:34 -04:00
< td >
2020-10-20 14:27:13 -04:00
< input name = " pass2 " type = " password " id = " pass2 " class = " regular-text " value = " " autocomplete = " off " aria - describedby = " pass2-desc " />
2020-10-20 15:07:10 -04:00
< ? php if ( IS_PROFILE_PAGE ) : ?>
< p class = " description " id = " pass2-desc " >< ? php _e ( 'Type your new password again.' ); ?> </p>
< ? php else : ?>
< p class = " description " id = " pass2-desc " >< ? php _e ( 'Type the new password again.' ); ?> </p>
< ? php endif ; ?>
2015-07-01 10:48:24 -04:00
</ td >
</ tr >
< tr class = " pw-weak " >
2015-07-08 17:28:25 -04:00
< th >< ? php _e ( 'Confirm Password' ); ?> </th>
2015-07-01 10:48:24 -04:00
< td >
2015-07-22 13:24:24 -04:00
< label >
2015-07-25 20:58:24 -04:00
< input type = " checkbox " name = " pw_weak " class = " pw-checkbox " />
2020-10-20 14:27:13 -04:00
< span id = " pw-weak-text-label " >< ? php _e ( 'Confirm use of weak password' ); ?> </span>
2015-07-08 17:28:25 -04:00
</ label >
2009-05-16 02:29:10 -04:00
</ td >
2008-03-10 18:09:26 -04:00
</ tr >
2018-08-16 21:51:36 -04:00
< ? php endif ; ?>
2014-11-13 10:21:21 -05:00
2018-08-16 21:51:36 -04:00
< ? php
if ( IS_PROFILE_PAGE && count ( $sessions -> get_all () ) === 1 ) :
?>
2014-12-16 04:15:23 -05:00
< tr class = " user-sessions-wrap hide-if-no-js " >
2015-07-22 16:50:25 -04:00
< th >< ? php _e ( 'Sessions' ); ?> </th>
2014-12-16 04:15:23 -05:00
< td aria - live = " assertive " >
2016-09-28 15:54:28 -04:00
< div class = " destroy-sessions " >< button type = " button " disabled class = " button " >< ? php _e ( 'Log Out Everywhere Else' ); ?> </button></div>
2014-12-16 04:15:23 -05:00
< p class = " description " >
< ? php _e ( 'You are only logged in at this location.' ); ?>
</ p >
</ td >
</ tr >
< ? php elseif ( IS_PROFILE_PAGE && count ( $sessions -> get_all () ) > 1 ) : ?>
2014-11-13 10:54:20 -05:00
< tr class = " user-sessions-wrap hide-if-no-js " >
2015-07-22 16:50:25 -04:00
< th >< ? php _e ( 'Sessions' ); ?> </th>
2014-11-21 11:25:23 -05:00
< td aria - live = " assertive " >
2016-09-28 15:54:28 -04:00
< div class = " destroy-sessions " >< button type = " button " class = " button " id = " destroy-sessions " >< ? php _e ( 'Log Out Everywhere Else' ); ?> </button></div>
2014-11-13 10:54:20 -05:00
< p class = " description " >
2015-07-22 16:50:25 -04:00
< ? php _e ( 'Did you lose your phone or leave your account logged in at a public computer? You can log out everywhere else, and stay logged in here.' ); ?>
2014-11-13 10:21:21 -05:00
</ p >
</ td >
</ tr >
2014-12-16 04:15:23 -05:00
< ? php elseif ( ! IS_PROFILE_PAGE && $sessions -> get_all () ) : ?>
2014-11-13 10:54:20 -05:00
< tr class = " user-sessions-wrap hide-if-no-js " >
2015-07-22 16:50:25 -04:00
< th >< ? php _e ( 'Sessions' ); ?> </th>
2014-11-13 10:21:21 -05:00
< td >
2016-09-28 15:54:28 -04:00
< p >< button type = " button " class = " button " id = " destroy-sessions " >< ? php _e ( 'Log Out Everywhere' ); ?> </button></p>
2014-11-13 10:54:20 -05:00
< p class = " description " >
< ? php
2019-09-02 20:41:05 -04:00
/* translators: %s: User's display name. */
2015-07-22 16:50:25 -04:00
printf ( __ ( 'Log %s out of all locations.' ), $profileuser -> display_name );
2014-11-13 10:54:20 -05:00
?>
2014-11-13 10:21:21 -05:00
</ p >
</ td >
</ tr >
2014-12-16 04:15:23 -05:00
< ? php endif ; ?>
2014-11-13 10:21:21 -05:00
2017-11-30 18:11:00 -05:00
</ table >
2005-09-13 20:03:02 -04:00
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
< ? php if ( wp_is_application_passwords_available_for_user ( $user_id ) ) : ?>
< div class = " application-passwords hide-if-no-js " id = " application-passwords-section " >
< h2 >< ? php _e ( 'Application Passwords' ); ?> </h2>
< p >< ? php _e ( 'Application passwords allow authentication via non-interactive systems, such as XML-RPC or the REST API, without providing your actual password. Application passwords can be easily revoked. They cannot be used for traditional logins to your website.' ); ?> </p>
2020-10-21 22:36:11 -04:00
< ? php
if ( is_multisite () ) {
2020-10-22 21:19:06 -04:00
$blogs = get_blogs_of_user ( $user_id , true );
$blogs_count = count ( $blogs );
if ( $blogs_count > 1 ) {
2020-10-21 22:36:11 -04:00
?>
< p >
2020-10-22 21:19:06 -04:00
< ? php
printf (
/* translators: 1: URL to my-sites.php, 2: Number of blogs the user has. */
_n (
'Application passwords grant access to <a href="%1$s">the %2$s blog in this installation that you have permissions on</a>.' ,
'Application passwords grant access to <a href="%1$s">all %2$s blogs in this installation that you have permissions on</a>.' ,
$blogs_count
),
admin_url ( 'my-sites.php' ),
number_format_i18n ( $blogs_count )
);
?>
2020-10-21 22:36:11 -04:00
</ p >
< ? php
}
}
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
App Passwords: Prevent conflicts when Basic Auth is already used by the site.
Application Passwords uses Basic Authentication to transfer authentication details. If the site is already using Basic Auth, for instance to implement a private staging environment, then the REST API will treat this as an authentication attempt and would end up generating an error for any REST API request.
Now, Application Password authentication will only be attempted if Application Passwords is in use by a site. This is flagged by setting an option whenever an Application Password is created. An upgrade routine is added to set this option if any App Passwords already exist.
Lastly, creating an Application Password will be prevented if the site appears to already be using Basic Authentication.
Props chexwarrior, georgestephanis, adamsilverstein, helen, Clorith, marybaum, TimothyBlynJacobs.
Reviewed by TimothyBlynJacobs, helen.
Merges [49752] to the 5.6 branch.
Fixes #51939.
Built from https://develop.svn.wordpress.org/branches/5.6@49754
git-svn-id: http://core.svn.wordpress.org/branches/5.6@49477 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-12-04 16:48:03 -05:00
if ( empty ( $_SERVER [ 'PHP_AUTH_USER' ] ) && empty ( $_SERVER [ 'PHP_AUTH_PW' ] ) ) {
?>
< div class = " create-application-password form-wrap " >
< div class = " form-field " >
< label for = " new_application_password_name " >< ? php _e ( 'New Application Password Name' ); ?> </label>
< input type = " text " size = " 30 " id = " new_application_password_name " name = " new_application_password_name " placeholder = " <?php esc_attr_e( 'WordPress App on My Phone' ); ?> " class = " input " aria - required = " true " aria - describedby = " new_application_password_name_desc " />
< p class = " description " id = " new_application_password_name_desc " >< ? php _e ( 'Required to create an Application Password, but not to update the user.' ); ?> </p>
</ div >
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
App Passwords: Prevent conflicts when Basic Auth is already used by the site.
Application Passwords uses Basic Authentication to transfer authentication details. If the site is already using Basic Auth, for instance to implement a private staging environment, then the REST API will treat this as an authentication attempt and would end up generating an error for any REST API request.
Now, Application Password authentication will only be attempted if Application Passwords is in use by a site. This is flagged by setting an option whenever an Application Password is created. An upgrade routine is added to set this option if any App Passwords already exist.
Lastly, creating an Application Password will be prevented if the site appears to already be using Basic Authentication.
Props chexwarrior, georgestephanis, adamsilverstein, helen, Clorith, marybaum, TimothyBlynJacobs.
Reviewed by TimothyBlynJacobs, helen.
Merges [49752] to the 5.6 branch.
Fixes #51939.
Built from https://develop.svn.wordpress.org/branches/5.6@49754
git-svn-id: http://core.svn.wordpress.org/branches/5.6@49477 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-12-04 16:48:03 -05:00
< ? php
/**
* Fires in the create Application Passwords form .
*
* @ since 5.6 . 0
*
* @ param WP_User $profileuser The current WP_User object .
*/
do_action ( 'wp_create_application_password_form' , $profileuser );
?>
< ? php submit_button ( __ ( 'Add New Application Password' ), 'secondary' , 'do_new_application_password' ); ?>
</ div >
< ? php } else { ?>
< div class = " notice notice-error inline " >
< p >< ? php _e ( 'Your website appears to use Basic Authentication, which is not currently compatible with Application Passwords.' ); ?> </p>
</ div >
< ? php } ?>
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
< div class = " application-passwords-list-table-wrapper " >
< ? php
$application_passwords_list_table = _get_list_table ( 'WP_Application_Passwords_List_Table' , array ( 'screen' => 'application-passwords-user' ) );
$application_passwords_list_table -> prepare_items ();
$application_passwords_list_table -> display ();
?>
</ div >
</ div >
< ? php endif ; ?>
2018-08-16 21:51:36 -04:00
< ? php
if ( IS_PROFILE_PAGE ) {
/**
Users: Change "Your Profile" and "My Profile" links in admin menu and toolbar to just "Profile" for consistency.
Props donmhico, bcworkz, seanchayes, mikeschroder, garrett-eclipse, akhileshsabharwal, ScottSmith, nacin, jenmylo, afercia, swissspidy, felix-edelmann, helen, melchoyce, karmatosed.
Fixes #26769.
Built from https://develop.svn.wordpress.org/trunk@47600
git-svn-id: http://core.svn.wordpress.org/trunk@47375 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-04-20 04:39:06 -04:00
* Fires after the 'About Yourself' settings table on the 'Profile' editing screen .
2018-08-16 21:51:36 -04:00
*
* The action only fires if the current user is editing their own profile .
*
* @ since 2.0 . 0
*
* @ param WP_User $profileuser The current WP_User object .
*/
do_action ( 'show_user_profile' , $profileuser );
} else {
/**
* Fires after the 'About the User' settings table on the 'Edit User' screen .
*
* @ since 2.0 . 0
*
* @ param WP_User $profileuser The current WP_User object .
*/
do_action ( 'edit_user_profile' , $profileuser );
}
?>
< ? php
2013-11-30 20:35:10 -05:00
/**
2018-08-16 21:51:36 -04:00
* Filters whether to display additional capabilities for the user .
2013-11-30 20:35:10 -05:00
*
2018-08-16 21:51:36 -04:00
* The 'Additional Capabilities' section will only be enabled if
* the number of the user ' s capabilities exceeds their number of
* roles .
2013-11-30 20:35:10 -05:00
*
2018-08-16 21:51:36 -04:00
* @ since 2.8 . 0
2013-11-30 20:35:10 -05:00
*
2018-08-16 21:51:36 -04:00
* @ param bool $enable Whether to display the capabilities . Default true .
2013-11-30 20:35:10 -05:00
* @ param WP_User $profileuser The current WP_User object .
*/
2018-08-16 21:51:36 -04:00
if ( count ( $profileuser -> caps ) > count ( $profileuser -> roles )
&& apply_filters ( 'additional_capabilities_display' , true , $profileuser )
) :
?>
2017-11-30 18:11:00 -05:00
< h2 >< ? php _e ( 'Additional Capabilities' ); ?> </h2>
2019-05-24 17:56:54 -04:00
< table class = " form-table " role = " presentation " >
2014-10-01 20:56:16 -04:00
< tr class = " user-capabilities-wrap " >
2013-03-18 09:27:57 -04:00
< th scope = " row " >< ? php _e ( 'Capabilities' ); ?> </th>
< td >
2018-08-16 21:51:36 -04:00
< ? php
$output = '' ;
foreach ( $profileuser -> caps as $cap => $value ) {
if ( ! $wp_roles -> is_role ( $cap ) ) {
if ( '' != $output ) {
$output .= ', ' ;
}
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
if ( $value ) {
2019-11-25 09:01:03 -05:00
$output .= $cap ;
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
} else {
2019-09-02 20:41:05 -04:00
/* translators: %s: Capability name. */
I18N: Improve translator comments.
* Add missing translator comments.
* Fix placement of some translator comments. Translator comments should be on the line directly above the line containing the translation function call for optimal compatibility with various `.pot` file generation tools. The CS auto-fixing, which changed some inconsistent function calls to multi-line function calls, is part of the reason why this was no longer the case for a select group of translator comments.
Includes minor code layout fixes.
Polyglots, rejoice! All WordPress core files now have translator comments for all strings with placeholders!
Props jrf, subrataemfluence, GaryJ, webdados, Dency, swissspidy, alvarogois, marcomartins, mihaiiceyro, vladwtz, niq1982, flipkeijzer, michielatyoast, chandrapatel, thrijith, joshuanoyce, FesoVik, tessak22, bhaktirajdev, cleancoded, dhavalkasvala, garrett-eclipse, bibliofille, socalchristina, priyankkpatel, 5hel2l2y, adamsilverstein, JeffPaul, pierlo, SergeyBiryukov.
Fixes #44360.
Built from https://develop.svn.wordpress.org/trunk@45926
git-svn-id: http://core.svn.wordpress.org/trunk@45737 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-09-01 13:13:59 -04:00
$output .= sprintf ( __ ( 'Denied: %s' ), $cap );
}
2018-08-16 21:51:36 -04:00
}
}
echo $output ;
?>
2013-03-18 09:27:57 -04:00
</ td >
</ tr >
</ table >
2018-08-16 21:51:36 -04:00
< ? php endif ; ?>
2008-03-11 18:03:05 -04:00
2010-10-17 14:24:34 -04:00
< input type = " hidden " name = " action " value = " update " />
2017-11-30 18:11:00 -05:00
< input type = " hidden " name = " user_id " id = " user_id " value = " <?php echo esc_attr( $user_id ); ?> " />
2010-10-17 14:24:34 -04:00
2018-08-16 21:51:36 -04:00
< ? php submit_button ( IS_PROFILE_PAGE ? __ ( 'Update Profile' ) : __ ( 'Update User' ) ); ?>
2010-10-17 14:24:34 -04:00
2004-08-01 05:13:50 -04:00
</ form >
</ div >
2018-08-16 21:51:36 -04:00
< ? php
2017-11-30 18:11:00 -05:00
break ;
2004-08-01 05:13:50 -04:00
}
2010-04-20 13:16:14 -04:00
?>
2012-07-03 09:27:14 -04:00
< script type = " text/javascript " >
2010-04-20 13:16:14 -04:00
if ( window . location . hash == '#password' ) {
document . getElementById ( 'pass1' ) . focus ();
}
</ script >
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
< ? php if ( isset ( $application_passwords_list_table ) ) : ?>
< script type = " text/html " id = " tmpl-new-application-password " >
2020-11-09 13:05:08 -05:00
< div class = " notice notice-success is-dismissible new-application-password-notice " role = " alert " tabindex = " -1 " >
2020-10-23 23:34:06 -04:00
< p class = " application-password-display " >
2020-11-09 13:05:08 -05:00
< label for = " new-application-password-value " >
< ? php
printf (
2020-11-11 05:41:07 -05:00
/* translators: %s: Application name. */
2020-11-09 13:05:08 -05:00
__ ( 'Your new password for %s is:' ),
'<strong>{{ data.name }}</strong>'
);
?>
</ label >
< input id = " new-application-password-value " type = " text " class = " code " readonly = " readonly " value = " { { data.password }} " />
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
</ p >
2020-11-09 13:05:08 -05:00
< p >< ? php _e ( 'Be sure to save this in a safe location. You will not be able to retrieve it.' ); ?> </p>
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
< button type = " button " class = " notice-dismiss " >
2020-10-23 23:34:06 -04:00
< span class = " screen-reader-text " >< ? php _e ( 'Dismiss this notice.' ); ?> </span>
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
</ button >
</ div >
</ script >
< script type = " text/html " id = " tmpl-application-password-row " >
< ? php $application_passwords_list_table -> print_js_template_row (); ?>
</ script >
< ? php endif ; ?>
2010-04-20 13:16:14 -04:00
< ? php
2020-02-06 01:33:11 -05:00
require_once ABSPATH . 'wp-admin/admin-footer.php' ;