I almost never read the comments on the WordPress page where the NAVT plugin is hosted – I usually don’t have the time to go over there and read through everything. So if you are looking for help and you’ve written something there chances are very good I’m not going to see it. The best way to get my attention is to contact me through the contact form or write to me at greg@atalayastudio[DOT]com – I usually answer fairly quickly.
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.
Lately, people have written to me asking me about supporting WordPress 2.8.5 or they tell me that NAVT isn’t working with 2.8.5 – I don’t have that problem. If you are STILL using IE (particularly IE8) then put it in compatibility mode or get FireFox (for the PC). I haven’t spent any time trying to figure out why IE8 doesn’t work if it ISN’T in compatibility mode (I’m not sure I care enough).
- Make sure the wp-root.php file is present in you NAVT installation directory.
- Make sure that there aren’t any other plugins that are interfering by deactivating all of your plugins (except NAVT) and see if it works. If it works, begin activating plugins until it stops working. Then contact the plugin writer and complain about what it is doing.
- Install Filefox and Firebug. Open Firebug, open the NAVT admin page and watch the Firebug console for Java Script errors.
You can contact me at greg @ gbellucci.us – I’ll try and help you if I can.
(this site runs wp 2.8.5 and navt 1.0.34- without issues)
User Comments