WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So I've create a custom walker for nav menu (i am talking about the menus located at: appearance -> menu -> add a new menu. I now use the following for several things i need: URL Title Attribute CSS Classes (optional) Description

My question is how do i change the labels of those fields to be more explanatory toward my uses.

So instead of title attribute for example it will say something like menus width

Thanks in advanced.

share|improve this question
So, you've hacked your menu so that the title is no longer the title attribute as it should be (for example)? – s_ha_dum May 20 '13 at 19:33
no The li still have title, however i pass a string in it that i later on(in the walker) break with explode and use it for other things.. For example Title Attribute = classname_filename_extention ....... so basically now in the walker i manipulate this string for whatever i need it.. which is irrelevant currently. however to be more descriptive to the user i want to change the labels according their uses. – Yaniv Kossas May 20 '13 at 19:37
up vote 1 down vote accepted

I don't have the time to work out a complete solution (which could be pretty complex) but, if I am reading things right, by default WordPress uses Walker_Nav_Menu_Edit to create those backend menus. It looks to me like you can build your own walker for the backend and pass it in via the wp_edit_nav_menu_walker hook.

If you did that, you should be able to not only rename those fields but add your own fields to keep things neat.

share|improve this answer
I am trying to refrain from hacking WP 's core classes/functions.. Is there no hook/filter for that ? if none i will just select your answer correct. – Yaniv Kossas May 20 '13 at 22:21
I did not say to hack core functions or classes. I said build a walker of your own and use the wp_edit_nav_menu_walker hook to tell WordPress to use your custom walker rather than the default one. This is the same thing you have already done with the custom walker for the front end display. There are no edits to core files involved in what I suggest. – s_ha_dum May 20 '13 at 22:26

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.