mirror of
https://github.com/WordPress/WordPress.git
synced 2024-11-04 18:01:42 +01:00
8f69ebf812
Some "visual tabs" in the WordPress admin used links wrapped in a `h2` heading. While these tabs look like ARIA tabs, they're just navigation menus and should be marked-up as such to be correctly exposed to assistive technologies. - changes the wrapping `<h2>` to a `<nav>` element: worth reminding `<nav>` elements also define ARIA landmarks - adds an `aria-label` to the `<nav>` elements so they can be distinguished from other `<nav>` elements in the page - adjusts the headings level in the Credits page Props audrasjb, afercia. Fixes #43398. Built from https://develop.svn.wordpress.org/trunk@44905 git-svn-id: http://core.svn.wordpress.org/trunk@44736 1a063a9b-81f0-0310-95a4-ce76da25c4cd
203 lines
10 KiB
PHP
203 lines
10 KiB
PHP
<?php
|
||
/**
|
||
* About This Version administration panel.
|
||
*
|
||
* @package WordPress
|
||
* @subpackage Administration
|
||
*/
|
||
|
||
/** WordPress Administration Bootstrap */
|
||
require_once( dirname( __FILE__ ) . '/admin.php' );
|
||
|
||
wp_enqueue_script( 'underscore' );
|
||
|
||
/* translators: Page title of the About WordPress page in the admin. */
|
||
$title = _x( 'About', 'page title' );
|
||
|
||
list( $display_version ) = explode( '-', get_bloginfo( 'version' ) );
|
||
|
||
wp_enqueue_style( 'wp-block-library' );
|
||
|
||
include( ABSPATH . 'wp-admin/admin-header.php' );
|
||
?>
|
||
<div class="wrap about-wrap full-width-layout">
|
||
<h1><?php printf( __( 'Welcome to WordPress %s' ), $display_version ); ?></h1>
|
||
|
||
<p class="about-text"><?php printf( __( 'Thank you for updating to the latest version!' ), $display_version ); ?></p>
|
||
|
||
<div class="wp-badge"><?php printf( __( 'Version %s' ), $display_version ); ?></div>
|
||
|
||
<nav class="nav-tab-wrapper wp-clearfix" aria-label="<?php esc_attr_e( 'Secondary menu' ); ?>">
|
||
<a href="about.php" class="nav-tab nav-tab-active"><?php _e( 'What’s New' ); ?></a>
|
||
<a href="credits.php" class="nav-tab"><?php _e( 'Credits' ); ?></a>
|
||
<a href="freedoms.php" class="nav-tab"><?php _e( 'Freedoms' ); ?></a>
|
||
<a href="freedoms.php?privacy-notice" class="nav-tab"><?php _e( 'Privacy' ); ?></a>
|
||
</nav>
|
||
|
||
<h2 class="feature-section-header"><?php _e( 'A Little Better Every Day' ); ?></h2>
|
||
|
||
<div class="feature-section headline-feature one-col">
|
||
<div class="col">
|
||
<div class="inline-svg">
|
||
<img src="https://s.w.org/images/core/5.1/update.svg" alt="">
|
||
</div>
|
||
<p><?php _e( 'You’ve successfully upgraded to WordPress 5.1! Following WordPress 5.0—a major release which introduced the new block editor—5.1 focuses on polish, in particular by improving overall performance of the editor. In addition, this release paves the way for a better, faster, and more secure WordPress with some essential tools for site administrators and developers.' ); ?></p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="feature-section one-col is-wide wp-clearfix">
|
||
<div class="col">
|
||
<h3><?php _e( 'Site Health' ); ?></h3>
|
||
<div class="inline-svg alignright">
|
||
<img src="https://s.w.org/images/core/5.1/site-health.svg" alt="">
|
||
</div>
|
||
<p><?php printf( __( 'With security and speed in mind, this release introduces WordPress’s first <a href="%s">Site Health</a> features. WordPress will start showing notices to administrators of sites that run long-outdated versions of PHP, which is the programming language that powers WordPress.' ), 'https://make.wordpress.org/core/2019/01/14/php-site-health-mechanisms-in-5-1/' ); ?></p>
|
||
|
||
<p><?php _e( 'When installing new plugins, WordPress’s Site Health features will check whether a plugin requires a version of PHP incompatible with your site. If so, WordPress will prevent you from installing that plugin.' ); ?></p>
|
||
|
||
<?php
|
||
$response = wp_check_php_version();
|
||
if ( $response && isset( $response['is_acceptable'] ) && ! $response['is_acceptable'] && current_user_can( 'update_php' ) ) :
|
||
?>
|
||
<p><em><?php _e( 'WordPress has detected your site is running an outdated version of PHP. You will see this notice on your dashboard with instructions for contacting your host.' ); ?></em></p>
|
||
<?php endif; ?>
|
||
|
||
<p><a class="button button-default button-hero" href="<?php echo esc_url( wp_get_update_php_url() ); ?>"><?php _e( 'Learn more about updating PHP' ); ?></a></p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="feature-section one-col is-wide wp-clearfix">
|
||
<div class="col">
|
||
<h3><?php _e( 'Editor Performance' ); ?></h3>
|
||
<div class="inline-svg alignright">
|
||
<img src="https://s.w.org/images/core/5.1/editor-performance.svg" alt="">
|
||
</div>
|
||
<p><?php _e( 'Introduced in WordPress 5.0, the new block editor continues to improve. Most significantly, WordPress 5.1 includes solid performance improvements within the editor. The editor should feel a little quicker to start, and typing should feel smoother. Nevertheless, expect more performance improvements in the next releases.' ); ?></p>
|
||
<?php if ( current_user_can( 'edit_posts' ) ) : ?>
|
||
<p><a class="button button-default button-hero" href="<?php echo esc_url( admin_url( 'post-new.php' ) ); ?>"><?php _e( 'Build your first post' ); ?></a></p>
|
||
<?php endif; ?>
|
||
</div>
|
||
</div>
|
||
|
||
<hr />
|
||
|
||
<h3 class="under-the-hood-header"><?php _e( 'Developer Happiness' ); ?></h3>
|
||
|
||
<div class="under-the-hood feature-section three-col">
|
||
<div class="col">
|
||
<h4><?php _e( 'Multisite Metadata' ); ?></h4>
|
||
<p>
|
||
<?php _e( '5.1 introduces a new database table to store metadata associated with sites and allows for the storage of arbitrary site data relevant in a multisite / network context.' ); ?>
|
||
<br>
|
||
<?php printf( __( '<a href="%s">Read more.</a>' ), 'https://make.wordpress.org/core/2019/01/28/multisite-support-for-site-metadata-in-5-1/' ); ?>
|
||
</p>
|
||
</div>
|
||
<div class="col">
|
||
<h4><?php _e( 'Cron API' ); ?></h4>
|
||
<p>
|
||
<?php _e( 'The Cron API has been updated with new functions to assist with returning data and includes new filters for modifying cron storage. Other changes in behavior affect cron spawning on servers running FastCGI and PHP-FPM versions 7.0.16 and above.' ); ?>
|
||
<br>
|
||
<?php printf( __( '<a href="%s">Read more.</a>' ), 'https://make.wordpress.org/core/2019/01/09/cron-improvements-with-php-fpm-in-wordpress-5-1/' ); ?>
|
||
</p>
|
||
</div>
|
||
<div class="col">
|
||
<h4><?php _e( 'New JS Build Processes' ); ?></h4>
|
||
<p>
|
||
<?php _e( 'WordPress 5.1 features a new JavaScript build option, following the large reorganization of code started in the 5.0 release.' ); ?>
|
||
<br>
|
||
<?php printf( __( '<a href="%s">Read more.</a>' ), 'https://make.wordpress.org/core/2018/05/16/preparing-wordpress-for-a-javascript-future-part-1-build-step-and-folder-reorganization/' ); ?>
|
||
</p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="under-the-hood feature-section two-col">
|
||
<div class="col is-span-two">
|
||
<h4><?php _e( 'Other Developer Goodness' ); ?></h4>
|
||
<p>
|
||
<?php _e( 'Miscellaneous improvements include updates to values for the <code>WP_DEBUG_LOG</code> constant, new test config file constant in the test suite, new plugin action hooks, short-circuit filters for <code>wp_unique_post_slug()</code> and <code>WP_User_Query</code> and <code>count_users()</code>, a new <code>human_readable_duration</code> function, improved taxonomy metabox sanitization, limited <code>LIKE</code> support for meta keys when using <code>WP_Meta_Query</code>, a new “doing it wrong” notice when registering REST API endpoints, and more!' ); ?>
|
||
<br>
|
||
<?php printf( __( '<a href="%s">Read more.</a>' ), 'https://make.wordpress.org/core/2019/01/23/miscellaneous-developer-focused-changes-in-5-1/' ); ?>
|
||
</p>
|
||
<p>
|
||
<a class="button button-default button-hero" href="<?php echo esc_url( 'https://developer.wordpress.org/' ); ?>"><?php _e( 'Learn how to get started' ); ?></a>
|
||
</p>
|
||
</div>
|
||
<div class="col">
|
||
<div class="inline-svg">
|
||
<img src="https://s.w.org/images/core/5.1/under-the-hood.svg" alt="">
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<hr />
|
||
|
||
<?php if ( ! file_exists( WP_PLUGIN_DIR . '/classic-editor/classic-editor.php' ) ) : ?>
|
||
<h2 class="feature-section-header"><?php _e( 'Keep it Classic' ); ?></h2>
|
||
|
||
<div class="feature-section one-col" id="classic-editor">
|
||
<div class="col">
|
||
<p><?php _e( 'Prefer to stick with the familiar Classic Editor? No problem! Support for the Classic Editor plugin will remain in WordPress through 2021.' ); ?></p>
|
||
<p><?php _e( 'The Classic Editor plugin restores the previous WordPress editor and the Edit Post screen. It lets you keep using plugins that extend it, add old-style meta boxes, or otherwise depend on the previous editor. To install, visit your plugins page and click the “Install Now” button next to “Classic Editor”. After the plugin finishes installing, click “Activate”. That’s it!' ); ?></p>
|
||
<p><?php _e( 'Note to users of assistive technology: if you experience usability issues with the block editor, we recommend you continue to use the Classic Editor.' ); ?></p>
|
||
<?php if ( current_user_can( 'install_plugins' ) ) { ?>
|
||
<div class="col cta">
|
||
<a class="button button-primary button-hero" href="<?php echo esc_url( wp_nonce_url( self_admin_url( 'plugin-install.php?tab=favorites&user=wordpressdotorg&save=0' ), 'save_wporg_username_' . get_current_user_id() ) ); ?>"><?php _e( 'Install the Classic Editor' ); ?></a>
|
||
</div>
|
||
<?php } ?>
|
||
</div>
|
||
</div>
|
||
|
||
<hr />
|
||
<?php endif; ?>
|
||
|
||
<div class="return-to-dashboard">
|
||
<?php if ( current_user_can( 'update_core' ) && isset( $_GET['updated'] ) ) : ?>
|
||
<a href="<?php echo esc_url( self_admin_url( 'update-core.php' ) ); ?>">
|
||
<?php is_multisite() ? _e( 'Return to Updates' ) : _e( 'Return to Dashboard → Updates' ); ?>
|
||
</a> |
|
||
<?php endif; ?>
|
||
<a href="<?php echo esc_url( self_admin_url() ); ?>"><?php is_blog_admin() ? _e( 'Go to Dashboard → Home' ) : _e( 'Go to Dashboard' ); ?></a>
|
||
</div>
|
||
</div>
|
||
<?php
|
||
|
||
include( ABSPATH . 'wp-admin/admin-footer.php' );
|
||
|
||
// These are strings we may use to describe maintenance/security releases, where we aim for no new strings.
|
||
return;
|
||
|
||
__( 'Maintenance Release' );
|
||
__( 'Maintenance Releases' );
|
||
|
||
__( 'Security Release' );
|
||
__( 'Security Releases' );
|
||
|
||
__( 'Maintenance and Security Release' );
|
||
__( 'Maintenance and Security Releases' );
|
||
|
||
/* translators: %s: WordPress version number */
|
||
__( '<strong>Version %s</strong> addressed one security issue.' );
|
||
/* translators: %s: WordPress version number */
|
||
__( '<strong>Version %s</strong> addressed some security issues.' );
|
||
|
||
/* translators: 1: WordPress version number, 2: plural number of bugs. */
|
||
_n_noop(
|
||
'<strong>Version %1$s</strong> addressed %2$s bug.',
|
||
'<strong>Version %1$s</strong> addressed %2$s bugs.'
|
||
);
|
||
|
||
/* translators: 1: WordPress version number, 2: plural number of bugs. Singular security issue. */
|
||
_n_noop(
|
||
'<strong>Version %1$s</strong> addressed a security issue and fixed %2$s bug.',
|
||
'<strong>Version %1$s</strong> addressed a security issue and fixed %2$s bugs.'
|
||
);
|
||
|
||
/* translators: 1: WordPress version number, 2: plural number of bugs. More than one security issue. */
|
||
_n_noop(
|
||
'<strong>Version %1$s</strong> addressed some security issues and fixed %2$s bug.',
|
||
'<strong>Version %1$s</strong> addressed some security issues and fixed %2$s bugs.'
|
||
);
|
||
|
||
/* translators: %s: Codex URL */
|
||
__( 'For more information, see <a href="%s">the release notes</a>.' );
|