Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter greg.siefert

    (@gregsiefert)

    That worked perfectly!

    The error goes away when you change line 466 of module.global-settings.php
    From the original:
    foreach ($custom_fields as $field) {

    To this:
    foreach ((array)$custom_fields as $field) {

    DavidWells — is this an appropriate change?

    Thread Starter greg.siefert

    (@gregsiefert)

    David — I am using the wp_nav_menu function.

    Here’s what I have:
    1) The Navigation radio buttons show on my template when I’m editing the landing page. Here is the code in my config.php of my custom template to set the Navigation option:
    array(
    ‘label’ => “Navigation Options”,
    ‘description’ => “Would you like to show or hide your site’s navigation on this landing page?

    Tip: Hiding navigation can increase conversion rates”,
    ‘id’ => ‘display-nav’,
    ‘type’ => ‘radio’,
    ‘default’ => ‘off’,
    ‘options’ => array(‘off’=>’Hide Navigation’,’on’=>’Show Navigation’),
    ‘context’ => ‘normal’
    )

    2) When I view the landing page, I can see that the value is being set to ‘on’ or ‘off’ appropriately. Here’s the code that I use to retrieve the value:
    $display_nav = lp_get_value($post, $key, ‘display-nav’);

    Here’s my question:
    I’m able to use the radio buttons and see that the value changes, but I don’t see where the value is used in WordPress to tell wp_nav_menu whether or not to display the menu. Where is the code that ties my display-nav setting to wp_nav_menu?

Viewing 3 replies - 1 through 3 (of 3 total)