WordPress.org

Support

Support » Plugins and Hacks » [Resolved] [Plugin: Nav Menu Roles] Fatal error

[Resolved] [Plugin: Nav Menu Roles] Fatal error

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author helgatheviking

    @helgatheviking

    What version of PHP are you using? What version of WP? Does this still happen if you disable other plugins? I cannot duplicate this locally or live, so I’m a bit stumped.

    edit:

    when stumped, turn to google. would you test out my version from github to see if this resolves your issue?
    https://github.com/helgatheviking/Nav-Menu-Roles/zipball/master

    Crandel

    @crandel

    Hi, I resolve bug removing the & from &$output in the two lines:
    parent::start_el( &$output, $item, $depth, $args );

    Anyway, I change the code because I have conflict with my theme. The theme add ‘wp_nav_menu_args’ filter too.

    Then I lose all menu format.

    What I do is remove the ‘wp_nav_menu_args’ filter and register to ‘walker_nav_menu_start_el’.

    And all work good.

    Plugin Author helgatheviking

    @helgatheviking

    Ok, that’s what I did to fix the bug too. I will push the update out to WordPress as soon as possible.

    Does your theme use a custom Walker with wp_nav_menu_args ? Because otherwise the $args should just be merged.

    Crandel

    @crandel

    Yes, it does.

    This problem occurs not only with your plugin, I saw same conflict with all plugins that manipulate menu.

    With yours, I understanding the problem.

    Plugin Author helgatheviking

    @helgatheviking

    Good to know. But yeah, you cannot use multiple Walkers. You could, however, adjust your theme to mimic the role-checking in my plugin.

    Plugin Author helgatheviking

    @helgatheviking

    please check out the 1.2 update. It uses an alternative method of restricting the menu items and will no longer conflict with a theme or plugin’s custom nav Walker.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘[Resolved] [Plugin: Nav Menu Roles] Fatal error’ is closed to new replies.