This evening I took a break from the development of Breadcrumb NavXT 2.1 and played with my GPX reader/plotter. Previously, on a 3.0Ghz Pentium 4 computer running linux and in Firefox 2.0 the maximum number of coordinates that can plotted using the GPolyline element was about 200. This was the max that maintained reasonable usability (the actual limit was somewhere in the 300s where it no longer rendered). With my laptop, a 2.8Ghz Core 2 Duo, still has a rather low limit of about 250 while maintaining usability. Some of my runs are over 300 track points, and these were not even that long of routes. I’m talking about somewhere between three and four miles.
Obviously this is not good, and that is why WP Trainer was not released last year. The solution to this problem is dynamic loading of the points, and using semi-sophisticated algorithms to remove “unneeded” points, such as ones that are outliers and ones that are in the middle of a straight line. Naturally, this is not a trivial thing to implement. Thus, it may be June before something is together for general consumption.
The latest development build of Breadcrumb NavXT now fully supports static front pages. Currently only the official WordPress method of defining a static front page is supported (using the options in Options>Reading). This was made possible thanks to some new conditional tags in WordPress 2.5. Thus, Breadcrumb NavXT 2.1 will require WordPress 2.5.
Next on deck is allowing breadcrumbs by tag or category. Categories would retain their current functionality, but tags will do what categories did in Breadcrumb Navigation XT. After that I’ll look into creating a widget for it. That will be the cutoff for 2.1, and I’ll do some code reduction as WordPress 2.5 will be a requirement so some old hacks can be removed. These are mainly located within the api file and only affect the administrative interface.
Version 2.1 will contain some major changes to the internal structure of the breadcrumb data object. Most of the API is not changing, and the changes are transparent for users of the administrative interface. Those who directly access the breadcrumb class will need to make sure to call assemble(); before display();. Failure to do so will result in unexpected behavior. These changes should be taken note of if using the latest SVN build of Breadcrumb NavXT, as it will be updated almost daily until things are ready.
Once the currently known bugs are worked out, which for the most part they are, the next order of business is getting things working correctly for static front pages. Static front pages will be supported via only one method of implementation for the time being. That method involves using the built in WordPress triggers, setting a page named home and setting the appropriate options in the administration panel under Options > Reading.
Even though 2.0.3 should have fixed the little PHP warning, it seems to not have. Fear not, this has been fixed in the SVN trunk. The other bug, which reveals it’s hideous head when activating the plug-in may be fixed as well. The error no longer gets thrown on the testbed, and it had to do with using require_once(); or include();. If anyone still receives either of these errors with the testing build please report it.
As an aside, Attachment NavXT won’t be developed. Later this month I’ll release the old code, but with the release of WordPress 2.5 it is no longer needed. In WordPress 2.5 there are some gallery functions that work with attachments, which is exactly what Attachment NavXT does.
Available immediately for public consumption is Breadcrumb NavXT 2.0.3. This is the third, and final, bug fix release for 2.0.x, next up for release is 2.1.0. In this version, some CSS code that was used for the administrative interface was removed as it also affected other aspects of the administration panel. Specifically, the “Write” tab was the one with the most visible problems. The code affecting the saving of the settings from the administrative interface has been tweaked, hopefully eliminating the
"Warning: strpos() [function.strpos]: Offset not contained in string. in …/breadcrumb_navxt_api.php on line 77"
bug. Finally, a variable dump of $usermeta is done when the “API Malfunction” error is triggered. Hopefully that will allow some additional insight as to a possible workaround to the problem. The cause of the malfunction is known but an automated workaround isn’t obvious at this time.
As March approaches and the release of WordPress 2.5 nears, development on Breadcrumb NavXT 2.1 begins. Right now in the SVN, the trunk received a minor update that won’t be tagged, though it’s version happens to be 2.0.3. The trunk SVN in never stable unless immediately following a tagged release. Version 2.1 will feature:
A newly revamped Administrative interface. Complies with the WordPress 2.5 guidelines, even though they recommend using tables in ways that they shouldn’t be.
Smarter method for trimming the title to stay within the maximum length while not cutting off in the middle word.
Reimplement static front pages.
Allowing post breadcrumb organization by category or tags.
A widgetized version. (May or may not make it in this version, not sure if it is appropriate for this plug-in.)
Hopefully, the current problems that some are experiencing when enabling the Administrative interface can be resolved in an elegant manor. One cause of this is known and an appropriate error message with instructions on how to resolve the issue will be given to the user.