I use the Path Breadcrumbs module to manage my site's breadcrumbs and since applying the Bootstrap 3.1 update, my breadcrumbs have all broken. It seems to me that the Path Breadcrumb module is being overridden by the Bootstrap breadcrumb settings. This wasn't happening before the update so I'm just making my assumption based on that. Any help or suggestions? Cheers.

Comments

jaydee1818 created an issue. See original summary.

markhalliwell’s picture

Title: Bootstrap theme overrides Path Breadcrumbs module » Add Path Breadcrumbs module support
Version: 7.x-3.1 » 7.x-3.x-dev
Category: Bug report » Feature request
Related issues: +#2313413: Microdata with Bootstrap 3 theme, +#2178565: Path_breadcrumbs warnings

The logic/code for bootstrap_breadcrumb() has not changed between 7.x-3.0 and 7.x-3.1. The only reason I can imagine happening is that you altered or removed this project's breadcrumb implementation and let the Path Breadcrumbs module take precedence.

In any case, there is currently no "official" integration/support for the Path Breadcrumbs module. This module implements a theme registry alter to use it's own theme function override (which isn't something that I personally think modules should be doing as it can cause a lot of issues for base themes like this).

That all being said, this isn't the first time this issue has come up and think maybe we should add support/use explicitly the Path Breadcrumbs theme function override if it exists.

  • markcarver committed 97cb5cb on 7.x-3.x
    Issue #2613764 by jaydee1818, markcarver: Add Path Breadcrumbs module...
markhalliwell’s picture

Status: Active » Fixed
jaydee1818’s picture

Just to clarify, I haven't altered or removed anything - it's a relatively new project and I'd just installed the Path Breadcrumbs module and Bootstrap theme as per usual. No custom code related to breadcrumbs in any custom module or template.php file and no hacking of either module, theme, or Drupal core.

PB module controlled breadcrumbs prior to update and no longer did after. Can't explain why this should be so but I guess it may just have something to do with the way that module is implemented that makes it incompatible. Cheers.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.