Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
Quick Navigation Interface provides a new way to navigate through the Administration Panels, combining the speed of keyboard shortcuts with the ease of a graphical user interface.
Just press g or ` — the backtick character, usually located above the tab key — to bring up the interface, and then start typing part of the name of any screen, post, page, etc. As you type, you’ll be shown a list of matching links. Use the Up and Down keys to move between them, and press Enter to open one.
This was inspired by Ubuntu’s Dash and HUD, and is also similar to the Spotlight feature in OS X.
I’m pressing `g` or the ` key, but nothing happens
There are a few likely causes for this:
The page hasn’t finished loading yet. Make sure you wait until the circle in the title bar has stopped spinning.
The cursor could be focused on an input field (like a text area or a button). Try clicking anywhere outside an input field (like the page’s background) to move the focus off of the input field, and then try to open the interface again.
If you’re not using an English keyboard, the key might not work. You can pick another key by following the instructions in the FAQ entry below. To help improve this for other non-English users, please let me know what a good key would be for your language.
You might be mistaking the ` (backtick) key for the ‘ (single-quote) key. You need to press the backtick key, which is normally located above the tab key and left of the 1 key. You can also try using the g key instead.
JavaScript execution might have been halted because of errors on the page, which would most likely be caused by the theme or another plugin. You can check your browser’s error console for details, and send the error to the plugin’s developer. To work around it, try disabling all other plugins temporarily, and switching to one of the Core themes, and see if that solves the problem. If it does, turn them back on one-by-one until you isolate which one is causing the problem.
Why doesn’t the content I’m searching for show up?
There are a few reasons why you may not see all content.
For performance reasons, only a limited number of posts are searched. The default is 500, and can be changed via the qni_content_index_params filter.
The search term must match the title of the content exactly. It doesn’t need to be the entire word, but it can’t be a typo or a “fuzzy” match.
You’ll only be shown content that your user account has permission to edit.
Can I customize the keyboard shortcuts and other options?
There isn’t a settings page, but all of the internal options can be modified via the qni_options filter. If you’re not familiar with using filters, you can learn more about them from the WordPress Plugin Developer’s Handbook, and then implement them in a functionality plugin that you write, or via a plugin like Functionality.
The values of the keys must correspond to JavaScript keyCodes, and the plugin doesn’t currently support using combinations. Be careful to choose keyCodes which are consistent across browsers.
How can I edit the JavaScript files?
Unfortunately modern JavaScript makes this more difficult than editing PHP, but there are instructions in the GitHub repository.
Is this plugin secure?
I’ve done my best to ensure that it is, but just in case I missed anything I also offer a security bounty for any vulnerabilities that can be found and privately disclosed in any of my plugins.
[NEW] Front end rebuilt in React, using Gutenberg’s library of UI components, the REST API, and local storage.
[FIX] Removed duplicate on-page links from the results.
[FIX] Fixed conflict with using backtick key within Gutenberg editor.
Breaking Changes:
[REMOVED] The ['shortcuts']['close-interface'] item in the array passed to the qni_options filter has been removed. QNI now uses the Modal component provided by Gutenberg, which only uses the Escape key to close it.
[REMOVED] The qni_template_path and qni_template_content filters have been removed, and files like qni-interface.php in your theme will no longer be used. This is because the plugin now declares the templates in React. There aren’t currently any plans to make them customizable.
