Cran-Berry Build 100

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.

-John Havlik

[end of transmission, stay tuned]

Tagged: ,
Updated:

Development

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.

Now onto Berry. Cranberry will be released sometime next week, preferably before May 1st. Currently, some tweaking to the styling needs to be done, especially for header images (logos), the search bar, and comments. Comments in general are getting overhauled. Right now this blog is still using the K2 comments.php, the only part that really isn’t my own code. This will be replaced by a new comments.php sometime this weekend. Then some hard core optimization needs to take place to speed up page load time and such. This first release will not have an Administrative interface for implementing modifications to it. The next release will contain options to change various things, centering around the amount of ‘flare’ the design has. Only one JavaScript line of code is in use right now, in the search bar. In the future more may be added and always these additions will be optional. Internet Explorer 8 still doesn’t play well with the theme, still need to figure out a centering method that it likes.

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:

  • PHP5
    • 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.

-John Havlik

[end of transmission, stay tuned]

Next Breadcrumb NavXT

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.

-John Havlik

[end of transmission, stay tuned]

Breadcrumb NavXT 2.1

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().

Find out more about the changes on the project page for Breadcrumb NavXT.

-John Havlik

[end of transmission, stay tuned]

WordPress 2.5

Somewhat of an unexpected release, 2.5 is now available. Released sometime this morning, WordPress 2.5 brings fixes to over 700 bugs. This includes a fix to the permalink bug for attachments that I mentioned previously in Permalink Problems. Attachments in general received some needed attention in 2.5 as well did the administrative interface. Most plug-ins that worked in 2.3 should work in 2.5, so don’t hesitate to upgrade to 2.5.

Breadcrumb NavXT 2.1 will be released by Wednesday April 2nd, 2008. I’m just doing some testing and tweaking. It seems that the install function is working again for it in 2.5. A widget version of the plug-in won’t make it until 2.2, but it is definitely on the road map.

As you may or may not have noticed, depending on browser caching, Cran-Berry is running on this blog now. There are still several things that need to be fixed, and as time progresses things will become cleaner and more feature filled. Some CSS tweaking will occur as well as some other changes to give the user some consistency between the Dashboard and it. Additionally the search form needs some lovin’.

-John Havlik

[end of transmission, stay tuned]