WordPress-C
/
WordPress
mirror of https://github.com/WordPress/WordPress.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix inline documentation syntax in a variety of DocBlocks and hook docs in `WP_Customize_Manager`. 

See [31370]. See #31888.

Built from https://develop.svn.wordpress.org/trunk@32032


git-svn-id: http://core.svn.wordpress.org/trunk@32011 1a063a9b-81f0-0310-95a4-ce76da25c4cd
This commit is contained in:
Drew Jaynes 2015-04-05 15:07:27 +00:00
parent 4b36885bbd
commit 831d7ea1e4
2 changed files with 17 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
wp-includes/class-wp-customize-manager.php
View File

@ -570,6 +570,7 @@ final class WP_Customize_Manager {
* Print CSS for loading indicators for the Customizer preview.
*
* @since 4.2.0
* @access public
*/
public function customize_preview_loading_style() {
?><style>
@ -768,7 +769,7 @@ final class WP_Customize_Manager {
do_action( 'customize_save_after', $this );
/**
* Filter response data for a successful customize_save Ajax request.
* Filter response data for a successful customize_save AJAX request.
*
* This filter does not apply if there was a nonce or authentication failure.
*
@ -801,17 +802,18 @@ final class WP_Customize_Manager {
}
/**
* Register any dynamically-created settings, such as those from $_POST['customized'] that have no corresponding setting created.
* Register any dynamically-created settings, such as those from $_POST['customized']
* that have no corresponding setting created.
*
* This is a mechanism to "wake up" settings that have been dynamically created
* on the frontend and have been sent to WordPress in $_POST['customized']. When WP
* on the frontend and have been sent to WordPress in `$_POST['customized']`. When WP
* loads, the dynamically-created settings then will get created and previewed
* even though they are not directly created statically with code.
*
* @since 4.2.0
*
* @param string[] $setting_ids The setting IDs to add.
* @return WP_Customize_Setting[] The settings added.
* @param string $setting_ids The setting IDs to add.
* @return WP_Customize_Setting The settings added.
*/
public function add_dynamic_settings( $setting_ids ) {
$new_settings = array();
@ -834,7 +836,7 @@ final class WP_Customize_Manager {
* @since 4.2.0
*
* @param false|array $setting_args The arguments to the WP_Customize_Setting constructor.
* @param string $setting_id ID for dynamic setting, usually coming from $_POST['customized'].
* @param string $setting_id ID for dynamic setting, usually coming from `$_POST['customized']`.
*/
$setting_args = apply_filters( 'customize_dynamic_setting_args', $setting_args, $setting_id );
if ( false === $setting_args ) {
@ -847,12 +849,13 @@ final class WP_Customize_Manager {
* @since 4.2.0
*
* @param string $setting_class WP_Customize_Setting or a subclass.
* @param string $setting_id ID for dynamic setting, usually coming from $_POST['customized'].
* @param string $setting_id ID for dynamic setting, usually coming from `$_POST['customized']`.
* @param string $setting_args WP_Customize_Setting or a subclass.
*/
$setting_class = apply_filters( 'customize_dynamic_setting_class', $setting_class, $setting_id, $setting_args );
$setting = new $setting_class( $this, $setting_id, $setting_args );
$this->add_setting( $setting );
$new_settings[] = $setting;
}
@ -1450,6 +1453,9 @@ final class WP_Customize_Manager {
* Add settings from the POST data that were not added with code, e.g. dynamically-created settings for Widgets
*
* @since 4.2.0
* @access public
*
* @see add_dynamic_settings()
*/
public function register_dynamic_settings() {
$this->add_dynamic_settings( array_keys( $this->unsanitized_post_values() ) );

2
wp-includes/version.php
View File

@ -4,7 +4,7 @@
*
* @global string $wp_version
*/
$wp_version = '4.2-beta4-32031';
$wp_version = '4.2-beta4-32032';
/**
* Holds the WordPress DB revision, increments when changes are made to the WordPress DB schema.