Guess what, WordPress 2.3 Beta 1 came out last week and after doing some initial testing, Breadcrumb Navigation XT will work as it currently does except for archives by tags. Since the default theme still has some work to be done to support tags properly, I will defer programming in support for tags until Beta 2 or 3. Feel free to do some playing around with WordPress 2.3 Beta 1 and Breadcrumb Navigation XT 1.9.3. And, by chance, if you find a bug report it please.
Oh, yeah, by the way, WordPress 2.3 as of Beta 1 does not support tags in syndication feeds, only categories.
Some users, while trying to use the new administration system for Breadcrumb Navigation XT, had problems with the breadcrumb displaying. These users happen to be running PHP4. Since both my development environment and my web server run versions of PHP5, it is not a simple task of maintaining full PHP4 compatibility. In order to regain PHP4 compatibility version 1.9.2 was released today with a fix which is both in bad style and potentially dangerous. I am seeking a more elegant solution but until then this will have to do. Beginning with Breadcrumb Navigation XT 2.0.0, the way the Administration interface is handled will change and will eliminate the current problem.
Holy GUIs, Batman! Yep, the new Breadcrumb Navigation XT administration panel/GUI is finished and distributed with the new version. Other than the administration panel, some tweaks were made involving the behavior for attachment posts (which are broken for certain permalink structures until WordPress 2.4), search pages, and date archive pages. Attachment posts are properly supported and recognized as an attachment of a post instead of a post in the ‘uncategorized’ category. Now in search pages, the search terms are output into the breadcrumb along with a customizable prefix and suffix replacing the single title of previous versions. Date archive pages when the year, month, and day are specified now allow three of the most common wording orders: big endian (ISO standard), middle endian (common in the US), and little endian (common in Europe).
The next major version 2.0.0 will contain major changes and support for WordPress 2.3. It will not be released until a WordPress 2.3 preview release has been released. 2.0.0 will nearly be rewritten from the ground up to address some performance concerns I have about the current code. These mainly pertain to unnecessary redundant branch statements that require some major work to fix. Until then, do grab Breadcrumb NavXT from its project page.
The previously mentioned problem with attachment posts is related to a permalink bug in WordPress. Permalinks containing categories (e.g., /archives/%category%/%postname%/) will pose problems for any attachment posts. This is due to the fact WordPress does not allow category management for these posts and thus they end up in the uncategorized category. If this category is not the primary category of the parent post, then the resulting permalink will break. A fix may already exist for 2.2. Regardless, I’ll keep digging into this so that 2.3 will not contain this problem.
Expect a beta for WP Trainer sometime near the end of this month, with a preview available on this blog in the coming weeks. Corresponding to this release I will rework moo.wp and the available download will correspond to the featured description. At the time of release API documentation for moo.wp will be available for theme and plug-in writers. Features described in the API documentation are guaranteed to remain the same for three WordPress major releases (e.g., 2.0.0, 2.1.0, 2.2.0, etc.) and will remain available for at least one year.
Breadcrumb NavXT is starting to get hits, Micheal did get a forward link going which has spurred that traffic. All of the various WordPress plug-in sites need to be updated, which means I probably have some e-mails to write. Anyways other that WordPress 2.3 support for 1.9, which includes the new tagging system, some more advanced length limiting techniques will be available. These include maximum total breadcrumb length and options on where and what to trim.
One last thing, I do realize that Internet Explorer 6 (and maybe 7) messes up the header on this blog, the simple solution to this is to at least upgrade to IE7, and think about switching to Firefox. Opera users will see that the footer is messed up, I am working on this but it may not be resolved for a week or so. I can not test for KHTML based browsers (e.g., Konqueror and Safari) right now so their status is unknown, but assumed to work.