Originally the concept was to be highly modular, allowing for flashy yet quickly loading design. This concept still has yet to be met, mainly due to a lack of time. Blu-Berry, a rather bastardized version of the vision for Berry, remains the incomplete theme powering this blog. Its introduction was a stop gate measure as WordPress 2.1 had some changes that broke the blog with the theme it replaced. Some have inquired on the link to download the theme. When the time comes Berry will be released to the masses.
Despite the incomplete implementation of the vision, I admire Berry (sounds awkward doesn’t it?). When messing around with a few of the images for the holiday season, with the transparencies and such, the thought crossed my mind about the future of this blog and what it will look like for the majority of next year. Nothing new will surface until the end of April, but a three column layout may not be out of the question. Those ugly “date badges” will receive much needed tweaking.
The crib will undergo some much needed organization in the meantime in preparation for changes present in the next Berry. Its a big task, and between other projects time for doing such things is scarce at best.
As Christmas approaches one bears early gifts. The first is the release of Iframe-B-Gone 1.0.0. It should greatly help in identifying and removal malicious code that is contained within the wp_posts database table.
This is the first plug-in that one’s written that utilizes the official WordPress way of localization, included in the zip archive is a .po file that can be used in writing translations. If you have created a translation and would like it to be included in the main distribution please leave a comment. Iframe-B-Gone can be downloaded on its project page.
Note that even though this software has been tested in a testbed, it may not be fully ready for production use. Before utilizing the cleaning functions please backup the infected posts, as if any data is lost, or erroneously removed one can not help in restoring that data. This plug-in comes with absolutely no warranty. Use this software at your own risk, and report any bugs that are found. Unless a serious bug is discovered no updates to this plug-in will be released until the first of next year (Breadcrumb NavXT needs some loving).
No bugs were reported for Beta 1, but I did find a problem with the way the breadcrumb was build for pages. Beta 2 fixes that and not much else. I need feedback and translators. There is now a SVN repository for Breadcrumb NavXT, its over at wp-plugins.org. This version also has a slightly different file structure, the main folder for Breadcrumb NavXT is now breadcrumb-navxt instead of breadcrumb-navigation-xt-2. The change corresponds to the assigned directory in wp-plugins.org.
Its here! The first beta of the new Breadcrumb NavXT 2.0. An improved administration interface now sports language files for enhanced localization support. Speaking of which, I need translators! I have created the english.php language file as a template, and started a bare-bones espanol.php (Spanish language file) which needs to be filled in with the translations from english.php. Breadcrumb NavXT, is located in many files under the breadcrumb-navigation-xt-2 folder, all localization files are located in the subfolder named languages. A new order of calling occurs in this version, and it shows up as two plug-ins in the plug-in menu, one “core” and one “administration interface”. If you intend to use the administration interface, only enable the administration interface plug-in as it will automatically load up the class located in the core file. Only enable the core plug-in if you are going to use the advanced method for integrating Breadcrumb NavXT into your blog, and you can figure out the differences for calling the differently named class. For basic users integration into your blog has not changed from the 1.10.x method.
You can grab the beta from the Breadcrumb Navigation XT page, or from the link below:
The beta is coming soon, very soon. I have a mostly functional version of the breadcrumb class working on my testbed, and tomorrow night I’ll get to work on the administration interface and creating the template for the language files. Then I’ll go back to tidying up loose ends in the class, and release a beta sometime tomorrow evening. So far, just about everything has been rewritten, and all custom wpdb queries were removed. This may cause a slight performance hit, but it should not be that big, unless the pages are very large, and this solves compatibility issues with some other plug-ins, namely the Polyglot plug-in. A the new hierarchical category system has been implemented, and there is now support for multi-paged searches, archives, and home pages. When the beta is released I will need testers that are willing to help debug the plug-in, as well as translators who are willing to write language files for the new administration interface.
Right now I need testers for:
Testing PHP4 compatibility (Even though I don’t officially support PHP4 anymore, I do try to keep things working in it)
Testing on blogs with various setups for static front pages, including the built in WordPress methods. It seems that the older versions still had bugs in regards to particular implementations of this, and it looked like the old code had some hacks that attempted to get things to work for static front pages. It’s time to get this working properly.
General testing, making sure options work as expected, etc.
Once the beta is out I request all bug reports be made in the post that it is announced in, this will keep the Breadcrumb NavXT page’s comment stream cleaner for once the plug-in is officially released.