[wp-trac] [WordPress Trac] #32832: Menu Customizer: Hook tracking

[WordPress Trac]

#32832: Menu Customizer: Hook tracking
------------------------------+--------------------
 Reporter:  celloexpressions  |       Owner:
     Type:  task (blessed)    |      Status:  new
 Priority:  normal            |   Milestone:  4.3
Component:  Customize         |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:
------------------------------+--------------------
Description changed by westonruter:

Old description:

> This ticket is to track remaining hook needs within Menus in the
> Customizer, to alleviate confusion, and a slew of duplicate tickets being
> opened to address various issues that sound different but are actually
> the same.
>
> Here is a summary of all places in the menus UI that should be hook-able,
> and the suggested approach to allowing devs to leverage these:
> - Menus Panel view - menu list, add new menu -> Customizer API
> (`add_section`)
> - Pre/post-menu name -> Customizer API (`add_control`)
> - Pre/post menu control/theme locations -> Customizer API (`add_control`)
> - Pre/post auto_add control -> Customizer API (needs to be re-split into
> a separate control) (`add_control`)
> - Screen Options -> existing filter `manage_nav-menus_columns`, should
> scope to Customizer when using, likely also requires some css when adding
> options
> - Menus help text -> Customizer API (`get_panel`, can also add to
> sections or elsewhere as needed)
> - Menu Locations section -> Customizer API (`add_control`)
> - Available items panel -> use `show_in_nav_menus` to show/hide post
> types/taxonomies, hooks to add custom sections (after Links or at bottom)
> handled in #32708
> - Menu item forms -> API or action to add custom options between
> description and original links (also needs support for saving the data as
> post meta), use CSS & screen options to hide core UI (to do). See #18584
> (and at least 5 duplicate tickets linked there). This is the primary
> thing that this ticket needs to address, and @westonruter has started
> thinking about implementation approaches.
>
> Current tasks remaining for implementing the above plan:
> - Separate the auto-add checkbox out from the menu control so that it can
> be removed or things added before/after it (this ticket)
> - Hooks for extending the available menu items panel (#32708)
> - Hooks/API for extending menu item controls/forms (this ticket)

New description:

 This ticket is to track remaining hook needs within Menus in the
 Customizer, to alleviate confusion, and a slew of duplicate tickets being
 opened to address various issues that sound different but are actually the
 same.

 Here is a summary of all places in the menus UI that should be hook-able,
 and the suggested approach to allowing devs to leverage these:
 - Menus Panel view - menu list, add new menu -> Customizer API
 (`add_section`)
 - Pre/post-menu name -> Customizer API (`add_control`)
 - Pre/post menu control/theme locations -> Customizer API (`add_control`)
 - Pre/post auto_add control -> Customizer API (needs to be re-split into a
 separate control) (`add_control`)
 - Screen Options -> existing filter `manage_nav-menus_columns`, should
 scope to Customizer when using, likely also requires some css when adding
 options
 - Menus help text -> Customizer API (`get_panel`, can also add to sections
 or elsewhere as needed)
 - Menu Locations section -> Customizer API (`add_control`)
 - Available items panel -> use `show_in_nav_menus` to show/hide post
 types/taxonomies, hooks to add custom sections (after Links or at bottom)
 handled in #32708
 - Menu item forms -> API or action to add custom options between
 description and original links (also needs support for saving the data as
 post meta), use CSS & screen options to hide core UI (to do). See #18584
 (and at least 5 duplicate tickets linked there). This is the primary thing
 that this ticket needs to address, and @westonruter has started thinking
 about implementation approaches.

 Current tasks remaining for implementing the above plan:
 - Separate the auto-add checkbox out from the menu control so that it can
 be removed or things added before/after it (this ticket) (#32820)
 - Hooks for extending the available menu items panel (#32708)
 - Hooks/API for extending menu item controls/forms (this ticket)

--

--
Ticket URL: <https://core.trac.wordpress.org/ticket/32832#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform