Crumbs calculates breadcrumbs for your site.
It does so by finding the parent of the current page, then the parent of the parent, etc, until it arrives at the home page.
Crumbs comes with a bunch of built-in plugins, that can be individually enabled, disabled and prioritized, and some of which provide further configuration options.
A lot of these are already enabled by default, and provide a behavior "as you would expect" out of the box. And as a fallback, with all plugins disabled, Crumbs behaves very similar to Easy breadcrumb.
Crumbs plugins have two responsibilities: (1) to determine the parent path for a given path, and (2) to determine the title for a specific breadcrumb link.
Besides, there are configurable token-based patterns to find the parent for entity pages per bundle.
As a fallback behavior, it will always try to find a parent by chopping off the last part of the path. And for the link title, the fallback is whatever was specified with hook_menu().
Fine-grained priority control
Most plugin priorities are further subdivided, to allow even more fine-grained control: By menu name (menu), vocabulary name (taxonomy), field name and entity bundle (entity reference), group content type (organic groups), etc.
A smart wildcard system saves you from having to configure each of those fine-grained priorities separately: You only sort as fine-grained as you need, the rest will take the priority of the parent.
Option to show or hide the breadcrumb item for the current page.
Option to show or hide the home link, and set a custom title for it (e.g. "Start" instead of "Home").
Option to show or hide breadcrumbs that only have one or two items.
Option for a custom separator.
Optional Microdata or RDFa support, so the breadcrumb will show up in Google / Bing / Yahoo search results.
(in the 7.x-2.x-microdata branch)
Option to override only specific implementations of THEME_breadcrumb().
- Documentation start page / Install and configure.
- Built-in plugins
- How it works. Technical and conceptual notes.
- API - build and register your own Crumbs plugins.
- Future roadmap.
Modules that leverage crumbs_get_trail()
- Menupoly (under construction) is a "clone" of Menu Block, which can use crumbs to determine which submenus should be expanded, and which items should be marked as "active" or "active trail". Very much what menu trails does, but more powerful.
- ThemeKey (D7) is supported by Crumbs, and in combination they allow to switch theme based on a parent path in the crumbs trail.
Meant as a feature-complete alternative to the following modules:
- Easy breadcrumb. In fact, if you disable all Crumbs plugins except the one for path aliases, the behavior should be very similar to Easy breadcrumb.
- Path breadcrumbs
- Menu breadcrumb
- Taxonomy breadcrumb
- Custom breadcrumbs
- Hansel breadcrumbs
- Node breadcrumb
- Menu trails. (in combination with Menupoly (see above).
There is a comparison page for different breadcrumb-related modules.
Feedback is welcome!
If you have any feedback, suggestions, interesting use cases, go ahead and post it on the issue queue!
Everything you post could lead to making this module better.
- Maintenance status: Actively maintained
- Development status: Under active development
- Module categories: Organic Groups (OG), Path Management, SEO, Site Navigation, Taxonomy
- Reported installs: 11,430 sites currently report using this module. View usage statistics.
- Downloads: 99,354
- Automated tests: Enabled
- Last modified: December 2, 2014