WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

#33324 closed defect (bug) (fixed)

Rename WP_New_Menu_Customize_Control

Reported by: DrewAPicture Owned by: helen
Milestone: 4.3 Priority: low
Severity: normal Version: 4.3
Component: Customize Keywords: has-patch commit
Focuses: Cc:

Description

In [32806], the WP_New_Menu_Customize_Control class was introduced. We should rename it to follow the WP_Customize_* convention that seems to be the standard for Customizer classes.

WP_New_Menu_Customize_Control => WP_Customize_New_Menu_Control

Basically all Customizer classes are named this way, save for two outliers introduced in 3.9 that we can't do anything about now anyway: WP_Widget_Area_Customize_Control and WP_Widget_Form_Customize_Control.

Related: #32576

Patch attached.

Attachments (1)

33324.diff (1.6 KB) - added by DrewAPicture 6 years ago.

Download all attachments as: .zip

Change History (4)

@DrewAPicture
6 years ago

#1 @ocean90
6 years ago

  • Keywords commit added
  • Priority changed from normal to low
  • Version set to trunk

This ticket was mentioned in Slack in #core by obenland. View the logs.


6 years ago

#3 @helen
6 years ago

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

In 33602:

Customizer: Rename WP_New_Menu_Customize_Control to WP_Customize_New_Menu_Control for consistency.

props DrewAPicture.
fixes #33324.

Note: See TracTickets for help on using tickets.