WPIntell

Source evidence

Usage code

LuckyWP ACF Menu Field · support · 2021-01-14T08:48:00+00:00

complaintsentiment
mediumseverity
0.92relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 31 rows with source links

16.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

26 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
decografics unresolved
How do i use this in the template? What code do i have to add to show the menu i selected? Regards Hi, I am also interested in this, how would I use this with Elementor what element should I use to call the custom field? I have tried text editor and heading but the field does not show. It shows on the page edit meta but not as a key to select whilst in the visual builder. Many thanks, and great plugin I’m gonna third this. I’m hunting for examples in the readme or plugin files but am having trouble pulling in the field. Thanks in advance! So, I think I figured this out. My issue was that I was trying to pull in the menu from a custom taxonomy and 1) had the ID field wrong and 2) didn’t have a menu selected (not sure how that happened). What I learned is that LuckyWP ACF Menu Field can still use the get_field() and the_field() functions like any other template that pulls in ACF fields uses. Where those two functions are added and what they look like will depend on what template file you are adding them to. For a menu field that is added to any page, you would go to the particular page you are trying to edit and make sure the menu is selected on that page. Once set, you can go to the page template (perhaps page.php) and add the_field('your_menu_fields_name'); . In my case, I was trying to pull in a menu that I had set for a custom taxonomy (not a page). So I needed to reference the taxonomy ID as well. So my function looked more like this: the_field('my_menu_field_name','customtaxonomyname_17'); The “my_menu_field_name” being set in the ACF field group settings in the dashboard, the “customtaxonomyname” being set in functions.php when I defined my custom taxonomy, and “17” being the ID of the taxonomy term I was trying to target. Hope that helps.

Comments

3 shown
mickyblu82 2021-01-25T15:50:00+00:00

Hi, I am also interested in this, how would I use this with Elementor what element should I use to call the custom field? I have tried text editor and heading but the field does not show. It shows on the page edit meta but not as a key to select whilst in the visual builder. Many thanks, and great plugin

steckinsights 2021-02-05T19:39:00+00:00

I’m gonna third this. I’m hunting for examples in the readme or plugin files but am having trouble pulling in the field. Thanks in advance!

steckinsights 2021-02-05T21:10:00+00:00

So, I think I figured this out. My issue was that I was trying to pull in the menu from a custom taxonomy and 1) had the ID field wrong and 2) didn’t have a menu selected (not sure how that happened). What I learned is that LuckyWP ACF Menu Field can still use the get_field() and the_field() functions like any other template that pulls in ACF fields uses. Where those two functions are added and what they look like will depend on what template file you are adding them to. For a menu field that is added to any page, you would go to the particular page you are trying to edit and make sure the menu is selected on that page. Once set, you can go to the page template (perhaps page.php) and add the_field('your_menu_fields_name'); . In my case, I was trying to pull in a menu that I had set for a custom taxonomy (not a page). So I needed to reference the taxonomy ID as well. So my function looked more like this: the_field('my_menu_field_name','customtaxonomyname_17'); The “my_menu_field_name” being set in the ACF field group settings in the dashboard, the “customtaxonomyname” being set in functions.php when I defined my custom taxonomy, and “17” being the ID of the taxonomy term I was trying to target. Hope that helps.