The second maintenance release for the 2.1 series, and this month’s release brings some useful bug fixes. Static front page support has been improved (serious testing of it’s functionality took place in the past month.). This includes automagical detection of static front pages, which will do all the heavy lifting for you. Paged items now work as they did in 2.0. Do note that paged item support is not complete (that’s getting thrown into the July 2.2.0 release). Additionally, the behavior of the link current item option has changed, now instead of trying to actually generate a link the href is left blank. This seems to be the best way to link to the current page, as it is the simplest method for implementation and is guarenteed to work 100% of the time. Of course, that may change again in the future.
When static front pages were reimplemented in Breadcrumb NavXT 2.1, it seems some things slipped through the cracks. In particular there is a problem with the frontpage breadcrumb, when on the frontpage. This and the options for static front pages were never cleaned up (my bad, I know). Another, relating to a /blog/blog and // error in the hyperlink for some by date archives was reported. Both of these will be fixed in this month’s service release, 2.1.2. For 2.2 support for WPMU will be improved (the administrative interface has problems with it right now), along with a widget. That release is a few months out still.
A little late, but fully functional. School work prevented the intended release date for Cran-Berry. Several styling, and code fixes were implemented which should provide a more uniform experience for most browsers. This includes new code for centering the content on the page, and some other general fixes. This release is not a full ‘stable’ release like a one for Breadcrumb NavXT, but this should be usable for advanced users. In the zip is two folders, one containing the theme, the other containing the modified version of WP-PageNavi. The other two recommended plug-ins should be downloaded from their respective home pages. Naturally, Berry implements support for these plug-ins in a safe manner–not having them will not cause PHP errors or warnings. Upon activation of the plug-ins they will display immediately (in most cases).
To change options, look in the functions.php and there will be a $berry_opts array of options a la Breadcrumb NavXT. These are documented in the source right above the corresponding option. Additionally, the sidebar is WordPress Widget aware.
Ok, so later today there will be a maintenance release of Breadcrumb NavXT, this will be version 2.1.1. The plan right now is to release a maintenance release each month with bug fixes and such. If enough new features are requested, a full version release will come out, and regardless a new version will always occur within a week of a new WordPress release. This release fixes some issues with the link current page option generating invalid HTML and some other bugs. Nothing in particular is slated for 2.1.2 yet, but it is reserved for any new bugs found in 2.1.1. 2.2.0 will add a widget for breadcrumbs to use with WordPress’ widget system.
Lastly, some progress on WP Trainer may occur this weekend. The most likely thing that will get done is database support and some basic administrative interface. Since GPX files tend to get very large, often over 2mb, PHP will not want to parse them correctly, thus an external command line based tool will be included (with source) to split up activities in the files so that they can be uploaded. The last order of business that needs to be solved is a problem with Google maps not liking when too many points are placed on a map. I’m still not sure how to fix this but I don’t think it’s something a little searching can’t fix. It appears the common approach is to drop many of the track points, which is not always acceptable, so smart dropping algorithms may need to be implemented. Currently, the server requirements for WP Trainer are shaping up as so:
XML parsing support
GD library support
Ability for PHP to write to files in a directory
I’m still debating if it is beneficial to dump the parsed GPX data into a database or not. It seems that it could dramatically increase database load and size, which is not always a good idea. Naturally, caching of data will be very important. Ideally, once a course is defined (named and has a track point map), any future runs on that course should automatically identify as using that course. This is very much a plaything project, which will take the backseat to all other paying or school projects. Development could always be expedited by sponsorship by a generous individual or organization.
A week and a day a go Breadcrumb NavXT 2.1 was released. So far only one new bug has appeared. This happens for users of PHP4, and an upcoming bug fix release, 2.1.1 will contain a fix for that. What’s in store for Breadcrumb NavXT 2.2? Officially, there is one big thing that should be implemented in it. That is support for paged pages/posts/archives/searches/etc. Currently, basic framework exists for supporting these pages, and even an option to enable rudimentary support which was added in 2.0. Full support for these page types needs to be implemented, which is the last “unconquered” frontier. A widget plug-in will also make it to 2.2. I’m setting the intended release of 2.2 to be sometime this summer, think around July. In 2.2 there will be some additional changes to the core plug-in as things are better organized and modularized within it.
The reason for placing the release of 2.2 in July is so that it allows some time for additional bugs to be caught and fixed along with allowing time to complete the documentation. If everything goes as planned, the documentation for Breadcrumb NavXT will be fully written some time in June (possibly sooner). Until then, there is always Berry to work on, which will be released at the end of this month. Additionally, WP Trainer may actually rear it’s head if time permits.