Breadcrumb hierarchy is opportunistically determined on taxonomy pages
solotandem - October 27, 2009 - 20:41
| Project: | Taxonomy Breadcrumb |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
From my reading of the code and testing it with different paths, it seems the code in _taxonomy_breadcrumb_term_page opportunistically determines the base of the breadcrumb path based solely on the first term id in the url. If there are multiple term ids in the url, the breadcrumb will only reflect the actual hierarchy if the first term is the deepest term.
Instead, should not the code determine the hierarchy from the actual relationships in the data?
#1
pretty much a duplicate of #616266: Breadcrumb hierarchy is opportunistically determined on node pages. Both can be handled in one issue.
#2
Similar results, but the cause is not a duplicate nor will the patch in #372813: Reordering taxonomy terms with drag-and-drop removes taxonomy breadcrumb path be a solution. The bug is caused by using the first term id in the url which is not guaranteed to be the deepest term. You can end up with one item in the breadcrumb trail when there should be more.