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.
Since the original author of Breadcrumb Navigation XT ran out of time for further development of the WordPress plug-in, I have picked it up. After a few days of coding and working on setting up the code section of this blog, the new version is ready for release. This new version, 1.8.0, includes support for author pages, and limiting the number of categories displayed in the breadcrumb.
Note that beginning with this release the version numbering scheme is to follow the same as WordPress uses, the first digit changes for major changes and as the second runs past 9. The second digit changes with the addition of features, internal structure of the class will not change in with a change in this digit. Finally, the third digit signifies a bugfix to features previously introduced without any added features. The next version, 1.9, is planned for the release of WordPress 2.3 due to the addition of tags into WordPress.
A certain reboot day rapidly approaches, and for the first time I am ready. In reality there are dozens of little bugs to fix and tuning to do, but for the most part things are falling into place for the new theme, berry. Right now nothing should be horribly broken, but there are no guarantees. Things happen, and when a theme is built from scratch (or nearly from scratch, currently the comments file is K2’s with modifications) bugs may exist.
Not much will change in appearance on the 1st of May except the application of the official mtekk ‘branding’ (read as the m logo appearing in the header). However, depending on how things go, and open beta may begin for blu-berry. Should the beta not become public on May first do not expect it until the middle of the month as the are a few more pressing projects that need attention.