By popular demand, Order Bender has received a substantial update. Now, rather than just working with categories, it will work with any hierarchical taxonomy on any post type (that is uses the taxonomy). Thus, now it is possible to specify a preferred custom taxonomy term for any post type for Breadcrumb NavXT.
Eventually, this will make it into the official WordPress.org plugin repository so everyone will get update notifications. Until then, you’ll have to manually update (by first deleting and then re-installing).
As part of the best practises for organizing your WordPress site so that Breadcrumb NavXT’s output is what you expect, having a post be a member of multiple category hierarchies is something you should not do. While it still isn’t something you should do, there is a way to specify which category hierarchy is more important for a specific post.
The idea is that the order of the categories being returned by get_the_terms() can be modifed so that the more important category hierarchy is output first. This takes advantage of Breadcrumb NavXT’s behaviour of choosing the first category (term) hierarchy it finds for a post.
This is where Order Bender comes in. Order Bender gives you a nice post meta box to select the primary category for a post, and will modify the output order of get_the_terms() accordingly. Simple as that.
Normally, flat post types such as the Post post type do not have parents. However, some people like to use pages for their hierarchy and want posts to be children of these pages. Typically, these pages have a description and then a post list based off of a category.
While I personally do not recommend this type of site structure, Breadcrumb NavXT has supported Pages as the parent of Posts for quite some time. The caveat has always been that setting the parent of the post was an exercise left to the user. I’ve just written a fairly basic plugin that removes that makes things easier. All it does is add a Parent metabox with a pages drop down to the edit screen for posts.
Unlike Google’s Breadcrumb micodata format, Schema.org’s microdata format for breadcrumbs is very easy to implement. There is no need for nested tags, or overly verbose and redundant tags. Instead, there is just two modifications from the standard Breadcrumb NavXT setup.
Breadcrumbs are a property of the Schema.org WebPage CreativeWork type. The first thing you must do to use the Schema.org microdata is declare the body of the (x)HTML page to be of type WebPage. You’ll need to modify your current WordPress theme so that the opening body tag is:
This is a really easy one. However, as I’ve been asked about it several times in the past few weeks, I’m going to post about it.
One way of using an image rather than just text for the home breadcrumb was covered in the Vista-Like Breadcrumbs for WordPress article back in 2009. However, that guide is more or less an advanced topic, and directly accesses the bcn_breadcrumb_trail class, something that is currently not recommended.
Since at least Breadcrumb NavXT 3.0, the settings page allows you to use valid HTML in some fields. In the future this will be more obvious due to settings page tweaks as it is not exactly obvious that this is possible. There are really only three steps to changing from text to an image for the home breadcrumb:
Go to the Breadcrumb NavXT settings page (under Settings > Breadcrumb NavXT).
On the “General” tab, look for the “Home Template” option.
Replace the text value of the “Home Template” option with the valid HTML for your image. e.g. <img src="http://YOUR_URL/YOUR_HOME_IMAGE" alt="Home"/> where YOUR_URL is the URL for your website, and YOUR_HOME_IMAGE is the name of the image, including file extension.
That’s it, and it also works for the “Blog Breadcrumb” and “Mainsite Breadcrumb” in setups that have these breadcrumb types.