Hate the WordPress NavWalker? Me too.
Navi is a developer-friendly alternative to the NavWalker. Easily build your WordPress menus using an iterable object inside of a template/view.
- PHP >= 7.0
Install via Composer:
$ composer require log1x/naviDownload the latest release .zip and install into wp-content/plugins.
Check out the examples folder to see how to use Navi in your project.
<?php
use Log1x\Navi\Navi;
$navigation = (new Navi())->build('primary_navigation');
if ($navigation->isEmpty()) {
return;
}
return $navigation->toArray();When building the navigation menu, Navi retains the menu object and makes it available using the get() method.
By default, get() returns the rawwp_get_nav_menu_object() allowing you to access it directly.
Optionally, you may pass a key and default to call a specific object key with a fallback have it be null, empty, or not set.
$navigation->get()->name;
$navigation->get('name', 'My menu title');If your menu item is linked to a page object (e.g. not a custom link) – you can retrieve the ID of the page using the objectId attribute.
# Blade
{{ get_post_type($item->objectId) }}
# PHP
<?php echo get_post_type($item->objectId); ?>In a scenario where you need to access a custom field attached directly to your menu item – you can retrieve the ID of the menu item using the id attribute.
Below we'll get a label override field attached to our menu using ACF – falling back to the default menu label if the field is empty.
# Blade
{{ get_field('custom_nav_label', $item->id) ?: $item->label }}
# PHP
<?php echo get_field('custom_nav_label', $item->id) ?: $item->label; ?>When calling build(), Navi will parse the passed navigation menu and return a fluent container containing your menu items. To return an array of objects, simply call ->toArray().
By default, build() calls primary_navigation which is the default menu theme location on Sage.
array [
5 => {
+"active": true
+"activeAncestor": false
+"activeParent": false
+"children": false
+"classes": "example"
+"dbId": 5
+"description": false
+"id": 5
+"label": "Home"
+"objectId": "99"
+"parent": false
+"slug": "home"
+"target": "_blank"
+"title": false
+"url": "https://sage.test/"
+"xfn": false
}
6 => {
+"active": false
+"activeAncestor": false
+"activeParent": false
+"children": array [
7 => {
+"active": false
+"activeAncestor": false
+"activeParent": false
+"children": array [
...
]
+"classes": false
+"dbId": 7
+"description": false
+"id": 7
+"label": "Example"
+"objectId": "101"
+"parent": 6
+"slug": "example"
+"target": false
+"title": false
+"url": "#"
+"xfn": false
}
]
+"classes": false
+"dbId": 6
+"description": false
+"id": 6
+"label": "Sample Page"
+"objectId": "100"
+"parent": false
+"slug": "sample-page"
+"target": false
+"title": false
+"url": "https://sage.test/sample-page/"
+"xfn": false
}
]That being said, depending on how deep your menu is– you can ultimately just keep looping over ->children indefinitely.
If you discover a bug in Navi, please open an issue.
Contributing whether it be through PRs, reporting an issue, or suggesting an idea is encouraged and appreciated.
Navi is provided under the MIT License.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent