After over a year sitting idle, Mtekk’s Testimonials is now available for public consumption. This initial public release brings a ton of fixes to the old testimonials plug-in originally written for the Weblogs.us front page (more on that later). Mtekk’s Testimonials is a modern WordPress plug-in, which requires WordPress 2.5 to function. Naturally, it has full i18n support (POT file coming soon). It sports Short Code tags for displaying testimonials on any WordPress post or page. When located on a front page, AJAX support is available (this limitation is changing in 1.1), which automatically changes to the next testimonial in 10 seconds (can be disabled by modifying the testimonials.js file).
User submission of testimonials is possible, and can be disabled. These submissions are never automatically approved for showing up in the testimonial stream. Along with this, the domain and TLD can be restricted for user testimonial submissions as a anti-spam measure (to be honest right now it is compulsory, this is changing in 1.1).
Next up on the update block is Iframe-B-Gone. Iframe-B-Gone is getting a full overhaul for it’s 1.1 release, the ETA for right now is by mid June. Then Breadcrumb NavXT’s June bugfix release, this will include some i18n related fixes as well as better handling of some “unique” category structures. WP Trainer is on hold until MooTools 1.2 is released.
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 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.
Holy taxonomy options Batman! With Breadcrumb NavXT you can now have breadcrumbs delimit posts by either hierarchical categories or linear tags. Improvements were also made in the max title trimming for posts. The administrative interface was heavily tweaked, as was the bcn_security function, it should no longer produce errors. On API malfunctions, instructions are now provided on a known method of fixing the problem. Lastly, attachments to pages will now show the full page hierarchy leading up to them, in contrast to attachments to posts which only show the parent post name. Also, WordPress 2.5 is required for this version, it fixed some things and made other things easier to implement.
Just a note to users that directly access the bcn_breadcrumb class, the method of displaying things has changed from 2.0. The class was heavily reorganized, again, to allow it to be more modular. You must call the member function assemble() before calling display().