Dani Llewellyn

<p>This plugin provides an API which allows the developer of a site to add custom fields on the default menu editor.</p>
<h4>Example Initialisation</h4>
<pre><code><?php
add_action('init', 'menu_excerpt__add_menu_field');
function menu_excerpt__add_menu_field() {
    if (!is_callable('bh_add_custom_menu_fields'))
        return;

    bh_add_custom_menu_fields(array(
        'excerpt' => array(
            'description' => 'Excerpt',
            'type' => 'textarea',
            )));
}
?>
</code></pre>
<h4>Accessing the fields</h4>
<p>The easiest way to access the field(s) you’ve added is to use something along the lines of:</p>
<pre><code>$menu = 'menuName';
$posts = wp_get_nav_menu_items($menu);
foreach ($posts as $p) {
    $myitem = get_post_meta($p->ID, '_menu_item_youritem', true);
    // do with $myitem what you like - it should be a string,
    // so the simplest thing is to "echo" it
}
</code></pre>
<p>you can use menu locations to get the menu name if you prefer – replace the first line above with:</p>
<pre><code>$locations = get_nav_menu_locations();
$menu = $locations['locationName'];
</code></pre>
<p>menu locations are useful if you like to swap your menus about.</p>
<p>Unfortunately these examples don’t allow the use of wordpress’ inbuilt menu walkers. To use those you will need to create a custom walker_nav_menu class and access the custom fields with something along the lines of (very stripped down example will need fleshing out for full walker functionality – there are tutorials on the net for custom nav walkers):</p>
<pre><code>class mywalker extends Walker_Nav_Menu {
    function start_el(&$output, $item, $depth, $args) {
        echo $item->custom_field
    }
}
</code></pre>
<p>The important bit here is that the field is placed on the second variable which behaves like an object. the custom_field part is the name you gave your field with dashes replaced with underscores (to allow the name to be used in an accessor).</p>
<h4>NOTE</h4>
<p>This plugin does nothing by itself. It provides an API only.</p>


Custom Menu Fields

Provides an API to add custom fields to the menu editor.

Jameel Moses

Roman Klabal

<p>Extends the ACF Flexible Content Field by transforming the layout list into a modal with image previews. Editing the fields layouts also happens in a modal for a better editing user experience.</p>
<h4>Image Conventions</h4>
<ul>
<li>The size of the image should be 730 x 300.</li>
<li>They should be named based on the layout’s name (<code>text_block</code>) with underscores converted to dashes (<code>text-block.jpg</code>).</li>
</ul>
<h4>Image Location</h4>
<p>Images should be placed in your theme. By default, images are located here: <code>THEME/lib/admin/images/acf-flexible-content-extended</code>.</p>
<p>Also note that you can filter this path, but it <strong>MUST</strong> be in your theme:</p>
<pre><code>add_filter( 'acf-flexible-content-extended.images_path', $path );
</code></pre>
<p><strong>NOTE:</strong> The path should not have a trailing beginning or trailing slash!</p>
<p>Additionally, you could filter all keys and/or images:</p>
<pre><code>add_filter( 'acf-flexible-content-extended.images', $images );
</code></pre>
<h4>Issues & Feature Requests</h4>
<p>If you identify any errors or have an idea for improving the plugin, feel free to open an <a href="https://github.com/jameelmoses/acf-flexible-content-extended/issues" rel="nofollow ugc">issue</a> or <a href="https://github.com/jameelmoses/acf-flexible-content-extended/pulls" rel="nofollow ugc">create a pull request</a>. Please provide as much info as needed in order to help resolving or approve your request.</p>


Flexible Content Extended for Advanced Custom Fields

Extends the ACF Flexible Content Field by transforming the layout list into a modal with image previews and editing in a modal for better UX.

Custom Menu Fields vs Flexible Content Extended for Advanced Custom Fields