Support taxonomy breadcrumbs in custom breadcrumbs 2

I have also just run into this issue. Custom Breadcrumbs will allow the use of the [termpath] token, but doesn't resolve it properly into separate links. It would be great if I didn't need to run Custom Breadcrumbs and Taxonomy Breadcrumb in tandem.

Sorry, I believe termpath is a product of the pathauto module. Custom breadcrumbs just uses the provided tokens - it doesn't make sense to try to alter them. As you indicate, taxonomy breadcrumb will already do what you ask, and it works well with custom breadcrumbs. For us to duplicate that code in custom_breadcrumbs may or may not be worthwhile. We are looking into doing something like this for custom breadcrumbs 2.

Subscribe

Subscribe

Correcting the version to match the title. Also subscribing :P

Subscribe

subscriberooni

I've written a first draft of the custom_breadcrumbs_taxonomy module now. Before releasing it for testing, I thought I should check to see if there are any features or use-cases that I might not be aware of. Here is what I have so far:

1. Provide breadcrumb trails based on lightest term, parent terms, and vocabulary on node pages and the taxonomy/term/tid pages.
2. Allow php to set breadcrumb visibility (with appropriate permission)
3. Allow taxonomy-based breadcrumbs for multiple languages
4. Provide centralized administration along with the node, paths, and views breadcrumbs.
5. Also allow taxonomy-based breadcrumbs to be created or modified on the taxonomy edit pages ( taxonomy/edit/term/tid and taxonomy/edit/vocabulary/vid). can't seem to do this while supporting multiple languages.
6. Select the node types to be considered (or excluded) for taxonomy-based breadcrumbs at admin/settings/custom-breadcrumbs.
7. Default "taxonomy breadcrumb" mode (available as a global configuration at admin/settings/custom-breadcrumbs) only permits customization of the links, using the taxonomy term and vocab names for the breadcrumb titles, and allowing one title/link per term. Breadcrumbs would be of the form [HOME] >> [VOCABULARY] >> TERM >> [TERM] , just as in taxonomy_breadcrumbs. Token replacement can be used in the path.
8. Also allow for "standard" custom breadcrumbs behavior (multiple titles/paths and using token replacement) on nodes with a matching vocabulary or term. These breadcrumbs can have multiple title/path pairs, and token replacements in titles and paths like all the other custom breadcrumb modules.

I am testing these items now and should be able to release within a week or so.

TODO items:

I think it might be helpful to be able select the vocab and/or term to use in taxonomy breadcrumb construction when editing a node with multiple vocabularies and taxonomy terms (with appropriate permission). This is essentially re-weighting the terms in the node, and this functionality may already be provided in other modules. If so there is no need to duplicate efforts provided the modules can work together.

Please respond and let me know what you think of this list. Which are most important/least important. Are there other features or use cases that should be considered.

I haven't used taxonomy breadcrumbs, so I can't compare both functionality, but I can say, from the list, it looks great!
I can't think of other items to suggest right now, maybe after playing with the module for a while...

Thank you!

Thanks. I've committed the new module custom_breadcrumbs_taxonomy to 6.x-2.x-dev for testing. Note that if you are using taxonomy breadcrumbs, it will copy your old breadcrumbs into the new custom_breadcrumbs_taxonomy tables when you install. After that you should disable taxonomy breadcrumbs.

For support requests and bug reports with this new feature, please open new issues.

Any idea when this feature will be part of a stable release? Or is there a patch I can apply against the current stable?
Thanks

Hi majnoona. Afraid the answers are no and no. If you are interested in helping move this toward a stable release, you can install 6.x-2.x-dev and test it out in a test environment (but best not in a production environment unless you are developer and enjoying living dangerously!).