WordPress Navigation List Plugin NAVT Plugin

The WordPress Navigation Tool (NAVT) plugin is a powerful tool designed to provide you with complete control over the creation, styling and contents of your web site’s navigation. The plugin gives you the ability to create unique site navigation from your pages, categories and users using a Drag ‘n Drop Interface; arrange the items within a group in any arbitrary order. Navigation groups may be composed of any combination of pages, categories, Authors, (Editors, Contributors, Subscribers), internal/external links and list dividers.

Plugin Features

• Navigation items can be duplicated and may appear in more than one group. Each item (even if duplicated) can be independently configured.
• List item names (called a menu alias) can be set to a name that differs from the name used as the page title or the category name.
• Create navigation items to be displayed in one of the following format:
  1. Text only
  2. Text over graphics
  3. Text with side graphic
  4. Graphic only
• Group items can be constructed to appear as a hierarchy – parent/child relationships can be formed between all types of items.
• Navigation menus may be styled using NAVT provided CSS classes, standard Word Press classes, or NAVT will apply user specified CSS classes.
• Supports BreadCrumb navigation.
• Supports navigation trees. Clicking a parent navigation item on a page reveals all child navigation on the subsequently displayed page.
• Navigation menus can be displayed (or not displayed) on any combination of user selected posts, pages, home page, archives, 404, search pages.
• Theme integration options allow you to insert a navigation group anywhere in your theme (without editing your theme).
• Create navigation using HTML Selects. Create multiple selects in a single group by using dividers.
• Embed navigation lists inside your posts and/or pages.
• Privacy settings for all navigation items and entire groups allows you to hide navigation items in a menu if the user is not logged into your site.
• Supports Gravatars for user navigation items.
• Transparently supports Word Press widgets.
• Built in help.
• Backup/Restore functionality.
• Compatible with the Word Press 2.5+ and Word Press MU
• Compatibility tested with IE6/IE7 (pc), Firefox (pc, Opera (pc), Firefox 2 (mac), Firefox 3 Beta 5 (mac), Swiftweasel
• NAVT IS NOT compatible with Safari

Localization

• English (en_US)
• German (de_DE) by Rico Neitzel
• Russian (ru_RU) by Dmitriy Kostromin
• Slovak (sk_SK) by Tomas Forro
• Japanese (ja_JA) by Yoichi Kinoshita
• Swedish (sv_SE) by Mikael Jorhult

• Belarusian (by_BY) by Marcis Gasuns

  If you’d like to contribute by offering your translating skills please contact me at greg @ gbellucci . us

  For more information, help, etc. Visit the NAVT Home Page

Change Log Information

Plugin change information is located on the Installation page

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

1. 

   Basic components of the NAVT administration page.

2. 

   Items are created in the Asset Panel by clicking a item in the select box and then dragging the item to a navigation group.

3. 

   Multiple copies of the same item can be created in the Asset Panel

4. 

   Copies can be placed into multiple groups.

Does NAVT provide a widget or a K2 sidebar module?

Yes. 5 NAVT widgets are transparently added when you activate the NAVT Plugin. The NAVT sidebar module is also transparently added to K2SBM if you are using the K2 theme.

How do I create horizontal menus at the top of my theme?

NAVT enables you to use your own classes by entering the CSS class information into the group options dialogbox. The group options dialogbox is indicated by the gear icon on the left side of any navigation group container. Write or obtain a CSS stylesheet that contains the classes for creating a horizontal menu (there are several sources available on the Internet). Integrate the CSS stylesheet with your theme style sheet. Note the style class names for the UL and LI tags that are used in the stylesheet and enter the names into the places provided under the group CSS options tab. Be sure to select: Do not apply CSS classes and check the Apply the CSS information below to this navigation group . This will force NAVT to apply the classes you’ve entered to the navigation group. Add the navigation group to the theme by using a widget, use the theme integration tab or by adding the navt function call directory to your theme.

How do I use NAVT Theme Integration?

NAVT theme integration allows you to add a navigation group into your theme without editing the theme. It does this by using an XPATH expression and applying one of the available actions: insert before, insert after, insert above, etc. An XPATH statment is used to identify a specific location within your theme where you’d like to put the navigation group. XPATH expressions use a combination of CSS selector ids and CSS classes to target a specific location within your theme. For example, if you wanted to place a navigation group at a specific location in your sidebar, you would formulate the necessary XPATH expression. If your sidebar had the selector id #sidebar and you wanted a navigation group to appear at the bottom of the sidebar the XPATH expression would simply be: #sidebar and you would use the insert bottom action.

CSS selector ids must begin with a # symbol and classes must begin with a single dot. You can also target locations using expressions like _#header div.main ul.menu This XPATH expression describes an unordered list with the class menu that is contained within a div that has the class named main that is contained with a container named header.

Here is a working example: to replace the top menu in a K2 theme with a NAVT navigation group:

Select the Theme Integration tab for the NAVT navigation group you want to use. Enter the following XPATH #page #header ul.menu and use the action Replace With. The navigation group will replace the standard K2 horizontal menu across the top of the theme.