I'll have to check my setup again, because when I looked, some entity tokens were not available via this module that were available in custom breadcrumbs. Particularly for entity reference fields, but I think also for a datetime field.

I think both modules have the same goals (but use different strategies), so you should join forces. Although I have not used both modules extensively, I think that PB can do what CB does, but also more.

@colan, I think we should do this way: I will provide all features that are missing from CB, and you will provide all features missing from PB. Then I will implement all missing features. How do you like this idea?

@colan, I think we should do this way: I will provide all features that are missing from CB, and you will provide all features missing from PB. Then I will implement all missing features. How do you like this idea?

Although I recently took over CB, I'm not overly familiar with it - I just wanted to help get some RTBCed issues committed, and put out some releases. So let's all start adding issues to the top of this ticket (as we create or become aware of them) like in #1624830: Plan for Entity Translation 7.x-1.0 release. Click on the edit tab here to add things to the list. I put a note to this effect on the CB project page so we should get more input on this soon.

So yes, let's collect all of the items, and then you can start implementing. ;)

RE #18, it is completely unclear to me how to provide the following solution:

Navigation:

Home
Home > Widgets
Home > Widgets > Widget A

Drupal elements:

Home url (node, whatever) <- handled by Drupal internally
Home url > Widgets view url <- arbitrary path as set in views, the (page, of nodes) view is a "section overview"
Home url > Widgets view url > Widget node url <- a node as listed in the view above

So, I want the Widgets link to appear on that page, and the Widgets and Widget A links to appear on the Widget A page, in the breadcrumbs. This is very simple in CB but I cannot work this out. The documentation needs more examples, if this is indeed possible.

Without path alias support, neither module can work for me. PB does not appear to support url alias which is a problem when the Pathauto modules is reporting over 480,000 installs. http://drupal.org/project/pathauto

I was about to use CB because I have used it before but now going to hold off until this is ironed out. URL alias is a requirement for most of my projects.

You can use node/%node for example or taxonomy/term/%term and breadcrumbs will apply to an alias. Using paths more useful, because they includes id's, and PB can use all data from node. For example you can build breadcrumbs based on node with needed term-reference (and rule will not apply to another nodes with another term-references). So i think PB is most flexible solution.

We can get a list of features in CB that are missing from PB, and
we get those features added to PB.
We can use this as a meta-issue to track all of these by maintaining the list in the description as we add items to it. Please all start coming up with the list items.

Colan,

I see that there's talk of deprecating Custom Breadcrumb for Path Breadcrumb. I hope you realise that the established user base of CB is 10x that of PB. You should probably consider integrating the other way instead... PB=>CB.

@susheel_c: Don't worry; I'm not planning on doing anything like that any time soon, but isn't it a great way to promote discussion on the issue? ;) Basically, I'm trying to herd folks into getting us down to one module in the long-term. It may never happen, but I'd at least like a clear understanding of what the differences are.

Path Breadcrumbs can be great UI for Drupal 8 breadcrumbs based on Condition Plugins API.
I had initial discussions about PB porting to Drupal 8 with @andypost. As I see it now, we should wait a little bit until https://www.drupal.org/project/page_manager will be ported.

Also, @Spleshka has an idea to move PB core to separate module so other modules will be able to use PB UI not only for breadcrumbs but for any other stuff they can imagine.

When we will be ready to start porting I will add all information and links on PB project page.
Any help will be appreciated!

Kate, thanks for the reply. As long as this will work with views and pathauto then I'm happy to see someone take it forward to D8. I really need a D7 solution right now and in a quandry. I'd rather go with PB if it will move on to D8, but need pathauto. Guess I'll be looking some more!

I'm not really a coder, so not sure what help I can be with the port. Let me know if you think of some way I can help.

Not sure breadcrumbs by path will do it. There is a discussion of its limitations and that is exactly my issue. I have a breadcrumb of Home > Publications > Journal, but there is no valid page for journal. I want to eliminate that component of the breadcrumb. Then, for the pages that come below that (Home > Publications > Journal > Spring 2014) I want to eliminate the Journal component from there as well.

I have a breadcrumb of Home > Publications > Journal, but there is no valid page for journal. I want to eliminate that component of the breadcrumb. Then, for the pages that come below that (Home > Publications > Journal > Spring 2014) I want to eliminate the Journal component from there as well.

If there are some relations between Publications, Journal and “Spring 2014” it can be done with Path Breadcrumbs. Even only these specific cases can be solved with PB, and other — with “Breadcrumbs by path”.

(I am silently following this thread, but don't want to hijack it too much)

The major drawback of PB which I see as unforgivable (in usability) is the lack of support for jquery_update. Even downgrading the admin interface to 1.5 PB breaks. Having a warning on the project page "Please, disable jQuery Update while working in Path Breadcrumbs UI!" should be an indication to stay away. Let's break the rest of the site while I get breadcrumbs working. Or not....

Thank you for your feedback. I absolutely agree that it's annoying bug. I hear similar complains almost every time I present PB on local events. PB uses some pieces of Rules JS code and we are keeping an eye on related Rules issue: #1810656: Rules UI does not work with JQuery 1.7+
Occasionally I dive into new stable and dev jQuery Update versions and fix compatibility problems. Any help is welcome here: #2066223: Isn't compatible with jQuery Update
In the next major PB release we will do our best to avoid using sensitive JS code.

For now the most common approach is to downgrade jQuery to 1.7 on admin pages and use Seven / Ember / Adminimal or other stable admin theme.