Hello,
I'm deeply in love with Drupal. My biggest wishlist is... breadcrumbs. I've struggled through many many sites where I've wanted to use the breadcrumbs desperately but ultimately had to pull them out and I think I finally have an idea for a resolution. I've also tried every hack and creative method that I've been able to find, to solve my problem - including taxonomy_context, the ideas and techniques documented by the fellow who created the distant-parent module, and more.

The main culprit sabataging my breadcrumbs is taxonomy.
I really love using taxonomies for lots of things. But taxonomies always show up in Breadcrumbs and I often do not want people to be able to click on a breadcrumb to open a taxonomy page which doesn't exist anywhere in the navigation and is likely to confuse them. I might never employ taxonomy list pages anywhere in a site, but still use it for things like having themable sections, building URLs using pathauto, and more.

Maybe the best idea would be to create a new breadcrumb.module that is entirely configurable based on the many methods people use to build their navigations (menu.module, taxonomy_context, book, etc.). But since that would be a lot of work (I would volunteer if I were a better coder!)...

But something simple could make a huge difference - What if, within the vocabulary configuration page, there was a setting that enabled you to "ignore breadcrumbs" for that vocabulary, meaning that no terms within would ever show up in a breadcrumb.

:)

Comments

sammos’s picture

Version: 4.6.3 » x.y.z

Just realized this should probably be filed with cvs instead of 4.6.3... thanks.

LAsan’s picture

Version: x.y.z » 7.x-dev

Feature request moving to cvs.

Sborsody’s picture

subscribe

firebird’s picture

This issue seems related: http://drupal.org/node/1495510 .

bojanz’s picture

Core breadcrumbs will never be flexible enough until we get something architecturally close to Crumbs in core (that's the module that solves in contrib, although with a pretty bad UI). I believe the plugin based approach is necessary to cover all of the use cases. Everything else is usually too use case specific.

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.