Some users of the Breadcrumb NavXT plug-in have noticed that upon trying the enter the administrative interface they are greeted by an error. Earlier version presented a “Bad user, no cookie for you” error, which should only be seen by malicious individuals. As of 2.0.1 this error was refined to letting the user know that part of the WordPress API on their blog is not working correctly. In particular, the get_currentuserinfo() function is malfunctioning. This is due to a shortcoming in WordPress in which the developers have know about and passed off as a plug-in problem since version 2.2. The cause is when WordPress is first installed, the default user that is created is set as an administrator, yet it has no usermeta in the database, hence has no user_level. This problem seems to be resolved by the upgrade functions in WordPress when upgrading from one version to another. Hence, fresh WordPress installs will have this bug, while older/upgraded ones will not. The best solution is to under the Users section and edit the user that is used primarily and make sure administrator is selected under role, then save. That should make the problem go away.

Tom Klingenberg has been working with me to fix some things up with the Breadcrumb NavXT. Our collaborated work will be present in version 2.0.2, which features several bug fixes. Included in 2.0.2 is the official German language file for Breadcrumb NavXT. Other major reworkings of the administrative interface will be included in 2.1.0. For all the users out there that need localization support, it is fully working in 2.0. thanks to the work of Tom. If there are any polyglots out there who could or have translated this plug-in, via the .po/.mo system, and would like their work to be included as part of the official package, leave a comment below. You can take a sneak peak at the 2.0.2 code by clicking the “Breadcrumb NavXT Latest Build” download link, be aware that the version number on this code may be incorrect and some things may be broken.

Lastly, anyone out there still using Breadcrumb Navigation XT of any version, please upgrade to Breadcrumb NavXT soon. On the 19th I will no longer offer any support for Breadcrumb Navigation XT and it’s project page may mysteriously vanish.

-John Havlik

[end of transmission, stay tuned]

It seems when I was playing around with Compiz, Compiz-Fusion, Emerald, and Avant Window Navigator, something in Gnome broke, now nautilus won’t load. I did however get some work done on Breadcrumb NavXT. Nautilus was not the only thing broken, poEdit broke as well. With poEdit broken I could not produce the .po file needed for the localization of the administration interface. Thus, I had planed on releasing something last night, which will be pushed off until tonight. I can’t say if it will be 2.0.0 or RC 1, right now I’ll refer to it as RC 1. I’ll do an actual release tag in the SVN for this release, and hopefully it will work nicely with the plug-in update notification built into WordPress 2.3.

One last word on RC 1, I know some documents may have stated that there will be uninstallation support for it. Since I in particularly do not like the current plug-in for doing that, I’ve decided to wait until WordPress decided to include it into their API (where it belongs I believe). What I don’t like about the current method is that it adds more work on the part of plug-in developers. The developer should not have to register with a separate entity the wp_options that it sets. Any of the values set using the set_option method should automatically register to the generating plug-in, as should any new entries created by update_option. Then the uninstallation part would be occur after the plug-in is deactivated, an uninstall button should pop-up, which will remove all of the DB entries used solely by the plug-in. The only entities that should have to be registered is any custom db tables created by the plug-in. Thus, 2.0 will not support this, and I will wait until things mature a bit before adding support in a future version of Breadcrumb NavXT which will correspond to the release of WordPress 2.5.

-John Havlik

[end of transmission, stay tuned]