Create WP_Customize_Control to separate the process of rendering a control from fetching, previewing, and saving its values. see #19910.

mirror of https://github.com/gosticks/wordpress-develop.git synced 2026-10-03 22:27:04 +00:00

Many-to-many mapping between settings and controls.
* Settings and controls have been separated in both the PHP (WP_Customize_Setting, WP_Customize_Control) and the JS (wp.customize.Setting, wp.customize.Control).
* While most settings are tied to a single control, some require multiple controls. The 'header_textcolor' control is a good example: to hide the header text, header_textcolor is set to 'blank'.

Add 'Display Header Text' control.

A handful of miscellaneous bugfixes along the way.

Notes:
* Controls should be separated out a bit more; juggling type-specific arguments in the switch statement is rather inelegant.
* Page dropdowns are currently inactive and need to be re-linked.

git-svn-id: https://develop.svn.wordpress.org/trunk@20295 602fd350-edb4-49c9-b593-d223f7449a82

This commit is contained in:

Daryl Koopersmith

2012-03-28 04:14:09 +00:00

parent 4337bd15e7

commit 2ca07cdf2a

8 changed files with 652 additions and 385 deletions

									
										wp-includes/js/customize-base.dev.js
									
		+1
		-1
	
												View File
												
				@@ -397,7 +397,7 @@ if ( typeof wp === 'undefined' )

						add: function( id, value ) {

							if ( this.has( id ) )

								return;

								return this.value( id );

							this._value[ id ] = value;

							this._value[ id ]._parent = this._value;