Changeset 20295 for trunk/wp-includes/class-wp-customize-section.php

Timestamp:

03/28/2012 04:14:09 AM (13 years ago)

Author:

koopersmith

Message:

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

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.

File:

• trunk/wp-includes/class-wp-customize-section.php (modified) (3 diffs)

trunk/wp-includes/class-wp-customize-section.php

@@ -16 +16 @@
     public $title          = '';
     public $description    = '';
-    public $settings;
+    public $controls;
 
     /**
@@ -36 +36 @@
         $this->id = $id;
 
-        $this->settings = array(); // Users cannot customize the $settings array.
+        $this->controls = array(); // Users cannot customize the $controls array.
 
         return $this;
@@ -85 +85 @@
             <ul class="customize-section-content">
                 <?php
-                foreach ( $this->settings as $setting )
-                    $setting->maybe_render();
+                foreach ( $this->controls as $control )
+                    $control->maybe_render();
                 ?>
             </ul>