Opened 14 years ago
Closed 10 years ago
#14414 closed feature request (duplicate)
Add an action hook to add fields to nav_menu items form
Reported by: | DreadLox | Owned by: | Gecka |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.1 |
Component: | Menus | Keywords: | has-patch |
Focuses: | Cc: |
Description
Hello,
In order to add a custom field to a nav menu item form, I have to setup a custom walker whereas a simple action hook could do the trick. Everything else is ok to handle and save the custom field. (http://loxdev.knc.nc/blog/wordpress/auto-populate-nav-menu-with-sub-pages/)
Here is how the asked action hook could be added:
http://github.com/loxK/Wordpress_Gecka_Submenu/blob/master/models/NavMenuHacks.php#L310-312
Attachments (1)
Change History (10)
#3
@
14 years ago
- Keywords has-patch added
- Owner set to Gecka
- Status changed from new to accepted
- Version set to 3.1
#5
@
13 years ago
Closed #18889 as a duplicate. It had ticket18889.patch which suggested a large number of new filters.
Is there any reason this one-line patch cannot be incorporated into 3.3 ...?
Because the time for feature requests / enhancements passed a while ago.
Note: See
TracTickets for help on using
tickets.
I think this should really be an alternative to the wp_edit_nav_menu_walker filter, which replaces the walker classname. This filter will cause clashes if multiple plugins change the classname of the walker. Only the last filter run will win.
This action would be a way for multiple plugins to add fields to the menu items (like is done with widget fields right now) and not have conflicts.