Plugin Directory

Test out the new Plugin Directory and let us know what you think.
!This plugin hasn’t 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.

WordPress Navigation List Plugin NAVT

Create, organize and manage your WordPress menus and navigation lists by logically grouping your pages, categories, users via a drag'n drop interface.

Classic WordPress and WordPress MU Plugin directory

  1. Download the plugin.
  2. Unzip the file in the WordPress directory: /wp-content/plugins/ - The plugin must reside in its own directory.
  3. Activate the NAVT plugin from the Word Press plugin page.
  4. After activating the plugin, go to the Manage menu and select the menu tab: NAVT Lists to use the plugin.
  5. NAVT requires the use of JavaScript (it must be turned on in your browser).

NAVT version 1.0.x+ will convert navigation groups created with previous versions to the new data format used by NAVT 1.0.x+. However, you should backup any current navigation groups using the NAVT plugin you have installed BEFORE installing and activating the new version of the plugin. NAVT backups are forward compatible with NAVT 1.0.x+ Click the ? (help) buttons provided on the NAVT List page to get help. More help is available in the NAVT Home Page The doc directory contains a single page manual explaining the PHP interface function call syntax.

Release Notes

*1.0.34 Release Candidate _(July 23, 2009)_

  1. Added Belarusian translation provided by Marcis Gasuns.
  2. Tested against wp 2.8.2

*1.0.33 Release Candidate _(July 12, 2009)_

  1. Adjustments made for user roles.
  2. Tested against wp 2.8.1

*1.0.32 Release Candidate _(May 26, 2009)_

  1. Fixed a problem in which carriage return/linefeeds are not removed from the JSON protocol string sent back to the client when returning menu group information. The carriage return/linefeed is contained as part of the string returned in a post or page title (new? as of 2.7.1). The carriage return/linefeed prevents the JSON code from correctly parsing the JSON protocol string and as a result the menu group box is not displayed.

*1.0.31 Release Candidate _(April 3, 2009)_

  1. NAVT now detects whether or not anchor urls should be secure or non-secure. (My thanks to Len Wilson)

*1.0.30 Release Candidate _(March 28, 2009)_

  1. include file change made for navtadmin.js.php. This is the only other file that requires wp-config.php to operate correctly. (My thanks to Audi for the help.)

*1.0.29 Release Candidate _(March 27, 2009)_

  1. Added chmod call to enable file writing in the NAVT plugin directory if the wp-root.php file is not present. Please read the note provided below.

NOTE: If you are not able to see the NAVT Lists menu item in the Word Press dashboard:

Due to the number of ways you can now install WordPress it has become more difficult to find the location of the wp-config.php file from the plugin directory. If NAVT cannot locate the wp-config.php file it will not work;

To resolve the problem, the file wp-root.php is dynamically created (by the NAVT plugin) and placed the directory where the NAVT plugin is installed. The file contains the name of the directory where you installed Word Press; this enables NAVT to later determine where to find wp-config.php. To create the wp-root.php file, NAVT requires WRITE permission in the NAVT installation directory. The plugin will attempt to set the directory permissions (0777) to enable it to write the file and then change the permissions to 0755 once the file has been created. If it cannot create the file, the plugin will not work. If you look in the directory where NAVT is installed and you don't see the file: wp-root.php, change NAVT's installation directory permissions to 0777 and reload your home page (from your browser). The wp-root.php file should appear. Change the permissions back to 0755 after the file has been created. If you change your WordPress installation directory, delete the wp-root.php file in the NAVT installation directory so the file can be recreated.

*1.0.28 Release Candidate _(March 23, 2009)_

  1. Fixed the issue with NAVT not correctly including the WordPress file wp-config.php when the wp installation is not the root directory OR if the WP_CONTENT directory has been moved.

*1.0.27 Release Candidate _(Dec 19, 2008)_

  1. Addition of Japanese localization (Thanks to Yoichi Kinoshita for the help.)
  2. Addition of Swedish localization (Thanks to Mikael Jorhult for his help.)
  3. Updates for role manager support.
  4. Updates to support Word Press 2.7
  5. Navigation Groups can be displayed (or not) on selected categories.
  6. Bug fixes
  7. Removed backup/restore until the next release
  8. A few visual updates

*1.0.26 Release Candidate _(May 15, 2008)_

  1. Fixes for supporting navt backup when used with Word Press MU

*1.0.25 Release Candidate _(May 14, 2008)_

  1. Minor changes for localization.
  2. Localization updates for Russian and Slovak. (German is in progress)
  3. Minor update that squeezes out space between tags in codeblocks.
  4. IE6 CSS adjustments.

*1.0.23 Release Candidate _(May 13, 2008)_

  1. Fixed problems with renaming groups.
  2. Renaming a group will update any widgets that refer to that group.
  3. Added a new misc item called a code block - enables you to insert HTML tags as part of a navigation list. Add images, headers, text, etc. between items.
  4. Added a new option that allows all navigation items to carry user entered HTML tags that can be inserted above, before, after or below a navigation item. see this article
  5. Fixed an issue with an ampersand in a title.
  6. A user CSS class can now be assigned to individual navigation item anchor.
  7. Updated the help information.

*1.0.22 Release Candidate _(April 26, 2008)_

  1. Added support for the role manager plugin.
  2. Rewrote the NAVT widget code to support multi-instance NAVT widgets. Any number of NAVT widgets can now be created.
  3. Localization updates
  4. Fixed sign-in/sign-out urls for Word Press installations that are not in the root directory
  5. Tested against WP 2.5.1

*1.0.21 Release Candidate _(April 24, 2008)_

  1. renamed the Slovak localization files from 'sz' to 'sk' - sorry!

*1.0.20 Release Candidate _(April 24, 2008)_

  1. Addition of Slovak localization (Thanks to Tomas Forro for his help.]
  2. All localization files updated.
  3. Minor changes to 'show on page' and 'show on post' group option.
  4. Tightened up code for backup and restore.
  5. Fix to adding uninstall/reset to the plugin page.
  6. Additional corrections to current page determination
  7. xpath updates

*1.0.19 Release Candidate _(April 22, 2008)_

  1. Minor fix for determining the current page

*1.0.18 Release Candidate _(April 22, 2008)_

  1. Put private and draft assets back into the asset list. These were accidently stepped on by another fix.

*1.0.17 Release Candidate _(April 18, 2008)_

Just not my day. Found and fixed a very bad problem that caused navigation groups to be completely deleted by saving a new page. Special thanks to Alex Leonard and Bradley Charbonneau for bringing this to my attention.

*1.0.16 Release Candidate _(April 18, 2008)_

  1. Sorry, I inadvertantly made 1.0.14 and 1.0.15 incompatible with WP 2.3+ by adding the shortcode function. Should be all better now...

Thank-you to GNR for the catch.

  1. Update for German localization

*1.0.15 Release Candidate _(April 18, 2008)_

Hopefully, this will be the last update for awhile... but I always think that.

  1. Fix to restore routine to add permalinks if pages are restored when a navigation group is restored.
  2. Update to embedded navigation list handler to use short codes.
  3. Fixes for theme integration.
  4. Better error handling when navigation groups are not configured.
  5. Corrections for adding class or selector ids to theme integration before/after group.
  6. Added several messages that will appear as HTML comments within your web page source code if a navigation group cannot be displayed on your blog. If you don't see a navigation group - check the source code for a NAVT MSG comment. The comment should indicate why the navigation group was not displayed or created. This feature can be turned on and off by checking or unchecking the new group option: "Show debug as comments in HTML source code". The debug output is off by default.

*1.0.14 Release Candidate _(April 17, 2008)_

  1. Update to restore routine.
  2. Corrections for page trees; routine could not readily determine the current page.

*1.0.12 Release Candidate _(April 12, 2008)_

  1. Update to Russian translation - Dmitriy Kostromin

*1.0.11 Release Candidate _(April 10, 2008)_

  1. Changed readme.txt and plugin header (still trying to force update notifications to work!)

*1.0.9 Release Candidate _(April 8, 2008)_

  1. Changed header in readme.txt to match plugin name to fix plugin update notification.
  2. Update to German localization. - Rico Neitzel

*1.0.8 Release Candidate _(April 6, 2008)_

  1. Added Russian localization (thanks to Dmitriy Kostromin for his help)
  2. Correction for escaping single quotations in link/alt strings (thanks to Troy Thompson for the heads up)

*1.0.7 Release Candidate _(April 3, 2008)_

  1. Added hierarchical representations to pages and categories in the asset select lists. Child page and child category names are displayed (in the Assets Panel) with the number of dash characters that corresponds to the child's relative postion - similar to the way they are displayed by Word Press. The relative position information is only for informational purposes and is not translated to represent the item's position in a navigation group.

  2. Added sorting capability to pages and category assets. Radio buttons have been added to the category and page select lists that enable you to change the sort order. Pages and categories can be sorted by 'title/name' or by 'menu order'.

  3. Added localized language code (I.E, en-US, de-DE, (contents of WPLANG value) ) browser name and browser version as additional NAVT menu classes. Browser names (firefox, msie, etc) are followed by the browser version as group classes. This is useful for creating CSS classes that are targetted for use with specific languages, browsers and browser versions. The German language for example, can sometimes contain more letters in an expression or sentence than English - applying a class that targets a specific language enables you to adjust container widths to prevent word wrapping.

  4. Browser class names:

* firefox * opera * msie * webtv * netpositive * mspie (MS Pocket Internet Explorer) * galeon * konqueror * icab * omniweb * phoenix * firebird * mozilla (Mozilla Alpha/Beta Versions) * amaya * safari * netscape

  1. Version information

* Version numbers always begin with a 'v' followed by the version number without the 'DOT' characters. Check by looking at the source code produced by the browser.

*1.0.6a Release Candidate _(March 30, 2008)_

  1. Corrections to the readme.txt : added screenshots.

*1.0.6 Release Candidate _(March 30, 2008)_

  1. Fix to text with side graphic output HTML.
  2. Corrected radio button selection for user navigation item (user or default avatar, gravatar)
  3. Fix to 'show on...' routines to correctly handle hide on selected pages and show on selected pages
  4. Changes to navt widget and navt sbm - no html output is written if navt_getlist() returns an empty list.

*1.0.5 Release Candidate _(March 29, 2008)_

  1. Fix to correctly allow dashes (-) in a navigation group name.

*1.0.4 Release Candidate _(March 27, 2008)_

  1. Fix for missing end of anchor tag for user defined URIs

*1.0.3 Release Candidate _(March 25, 2008)_

  1. '#wpcontent select' height was changed in WP 2.5 RC1.1 - this caused NAVT selects to display incorrectly. Set the NAVT css stylesheets to change the select height to auto.

*1.0.2 Release Candidate _(March 23, 2008)_

  1. Fixed the version information
  2. Added backup your data reminder to the installation page

*1.0.1 Release Candidate _(March 23, 2008)_

  1. Major rewrite - Brand new interface, new options

Requires: 2.5 or higher
Compatible up to: 2.8.2
Last Updated: 8 years ago
Active Installs: 2,000+


0 out of 5 stars


Got something to say? Need help?


Not enough data

0 people say it works.
0 people say it's broken.

100,1,1 29,7,2
0,1,0 20,5,1
100,1,1 56,9,5