Changes between Initial Version and Version 2 of Ticket #27315
- Timestamp:
- 06/18/2014 05:24:55 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #27315
- Property Focuses ui removed
-
Property
Component
changed from
Administration
toAppearance
-
Property
Version
changed from
3.8.1
to3.4
-
Property
Milestone
changed from
Awaiting Review
toFuture Release
- Property Keywords good-first-bug needs-patch added
-
Ticket #27315 – Description
initial v2 1 WP_Customize_Section uses `$keys = array_keys( get_class_vars( __CLASS__ ) );` to set class variables, but WP_Customize_Controluses `$keys = array_keys( get_object_vars( $this ) );` to set class variables.1 `WP_Customize_Section` uses `$keys = array_keys( get_class_vars( __CLASS__ ) );` to set class variables, but `WP_Customize_Control` uses `$keys = array_keys( get_object_vars( $this ) );` to set class variables. 2 2 3 The difference is that if you extend WP_Customize_Controlyou can add new class variables by setting them in the extended class and passing them to the args array in the constructor.4 In WP_Customize_Sectionone has to override the constructor to do the same.3 The difference is that if you extend `WP_Customize_Control` you can add new class variables by setting them in the extended class and passing them to the args array in the constructor. 4 In `WP_Customize_Section` one has to override the constructor to do the same. 5 5 6 6 changing 7 `$keys = array_keys( get_class_vars( __CLASS__ ) );` 7 {{{ 8 $keys = array_keys( get_class_vars( __CLASS__ ) ); 9 }}} 8 10 to 9 `$keys = array_keys( get_object_vars( $this ) );` 10 in WP_Customize_Section would solve the problem (or use the static keyword which would raise the requirements to PHP 5.3) 11 {{{ 12 $keys = array_keys( get_object_vars( $this ) ); 13 }}} 14 in `WP_Customize_Section` would solve the problem (or use the static keyword which would raise the requirements to PHP 5.3)