mirror of
https://github.com/WordPress/WordPress.git
synced 2024-11-05 10:22:23 +01:00
b1804afeaf
Also use 'back-compat' in some inline comments where backward compatibility is the subject and shorthand feels more natural. Note: 'backwards compatibility/compatibile' can also be considered correct, though it's primary seen in regular use in British English. Props ocean90. Fixes #36835. Built from https://develop.svn.wordpress.org/trunk@37431 git-svn-id: http://core.svn.wordpress.org/trunk@37397 1a063a9b-81f0-0310-95a4-ce76da25c4cd
19 lines
488 B
PHP
19 lines
488 B
PHP
<?php
|
|
/**
|
|
* WordPress Options Header.
|
|
*
|
|
* Displays updated message, if updated variable is part of the URL query.
|
|
*
|
|
* @package WordPress
|
|
* @subpackage Administration
|
|
*/
|
|
|
|
wp_reset_vars( array( 'action' ) );
|
|
|
|
if ( isset( $_GET['updated'] ) && isset( $_GET['page'] ) ) {
|
|
// For back-compat with plugins that don't use the Settings API and just set updated=1 in the redirect.
|
|
add_settings_error('general', 'settings_updated', __('Settings saved.'), 'updated');
|
|
}
|
|
|
|
settings_errors();
|