It would be good to have a select field for all of the wordpress menus created in appearance > menus.
Some of the websites I’m working on require the ability to create and set custom menus for a given page. I’m currently dealing with this by listing all menus in a standard select element. However this is not dynamic and needs updating whenever a menu is added or deleted. In short there’s currently no easy way (that I’m aware of) to allow an end user to change menus on a given page through WP.
The field output could be the menu ID, slug, name or object, depending on how the field is set up.
As a more general question, if someone has built a third party add-on does that reduce the likeliness that it will ever be built into the ACF core? I’m very grateful that people build these add-ons, but I’d be interested to know what parameters are considered before something is built into ACF as oppose to someone building it as an add-on.
That I’m not sure about. I suppose it’s partly to do with what will be used by the most people. I like the add-on system because helps keep the core plugin lighter. I honestly don’t like using plugins that try to cram everything possible in because they start to get bloated. While I use things like the repeater field on almost every site I build, I’ve only needed to allow the selection of menus on 1 of the many sites I’ve built.
Viewing 4 posts - 1 through 4 (of 4 total)
The topic ‘Field for WordPress Navigation Menus’ is closed to new replies.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users