WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#29959 closed defect (bug) (fixed)

Twenty Fifteen: Move the custom Customizer class to its own file.

Reported by: kwight Owned by: iandstewart
Milestone: 4.1 Priority: normal
Severity: normal Version: 4.1
Component: Bundled Theme Keywords:
Focuses: Cc:

Description

Let's separate out the control class to its own file, so its treated more like core treats classes. This also simplifies customizer.php and removes the need for altering hook priorities.

Attachments (1)

29959.diff (4.0 KB) - added by kwight 5 years ago.

Download all attachments as: .zip

Change History (6)

@kwight
5 years ago

#1 @obenland
5 years ago

  • Component changed from Themes to Bundled Theme

It should become obsolete once the scripts are moved.

cainm said this:

you can get rid of the custom control and then enqueue the js on the customize_controls_enqueue_scripts action
but I didn't have time to narrow down the control extension past: wp.customize.controlConstructor.select

#2 @kwight
5 years ago

Yay! How quickly I forgot about that :)

#3 in reply to: ↑ description @cainm
5 years ago

Related: #29982

#4 @iandstewart
5 years ago

  • Owner set to iandstewart
  • Resolution set to fixed
  • Status changed from new to closed

In 29944:

Twenty Fifteen: Removing unused custom color controls.

Props cainm, fixes #29982 and #29959.

#5 @SergeyBiryukov
5 years ago

  • Milestone changed from Awaiting Review to 4.1
Note: See TracTickets for help on using tickets.