Archive for the 'NAVT' Category

Plugin Compatibility – Really?

Published
by
Greg
on October 31, 2009
in NAVT and Word Press
. Closed

You may have seen the new  Plugin Compatibility box on the plugin pages hosted by wordpress.org. The box allows users to select their WordPress release AND the plugin release and choose between a Working or Broken selection for the plugin.

So my question is this… What is really broken? WordPress or the plugin? Does the user really know for sure? Could it be another plugin that is causing the problem? Is it the browser? Does this really give an accurate accounting of a plugin’s compatibility? I honestly don’t think so.

Continue reading ‘Plugin Compatibility – Really?’

NAVT Update 1.0.33

Published
by
Greg
on July 12, 2009
in NAVT and Tips/Hints
. 14 Comments

Contains a minor change for user roles and was tested against wp 2.8.1. If you are having trouble finding the NAVT List menu item once the plugin is activated I suggest you do the following:

  • Temporarily change the permissions on the NAVT directory to 777.
  • Reactivate the NAVT plugin.
  • Change the NAVT directory permissions to 755

As of version 1.0.29, NAVT needs to create a file in it’s own installation directory – the file is only created once. If it can’t create the file then it will not display the NAVT List menu item.

You may find that the Word Press automatic plugin upgrade routine removes all files from the previous version and you may have to temporarily change the permissions on the NAVT directory after upgrading. Make sure you change the permissions back to 755 after activating the plugin.

Notes on NAVT 1.0.28 and 1.0.29

Published
by
Greg
on March 27, 2009
in NAVT and Tips/Hints
. 5 Comments

Since the release of WordPress 2.7, people now have the ability to install WordPress in ways that make it difficult for the NAVT plugin to determine the location of the WordPress file wp-config.php. The ajax portion of NAVT includes the wp-config.php file so it can use all of the features and functions provided by the WordPress core code. If NAVT can’t find the file because the WordPress installation isn’t where it would normally be located (in the root directory) OR the WordPress wp-content directory is NOT located inside the WordPress installation directory then NAVT has no chance of working correctly. Continue reading ‘Notes on NAVT 1.0.28 and 1.0.29′