I have a vocabulary that uses taxonomy to make a hierarchy.
Its something like:
State
-Region-A
--Subregion-1
--Subregion-3
-Region-B
--Subregion-2
I am using a bunch of different page views to aggregate content by each region level; using "Taxonomy: Term ID (with depth)" to do the views (I have also tried parent term, but the outcome is the same.)
All the breadcrumbs work well with my views except for at the state level, where a child term is appearing in the breadcrumb.
EX: State Name > Region-A
When it should simply be: State Name
I am not sure what the issue is.
Thanks
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | cb_view_arguments_patch.diff | 2.4 KB | MGN |
| #4 | cb_view_arguments_patch.diff | 2.4 KB | MGN |
Comments
Comment #1
MGN commentedCan you explain how you have set up the breadcrumb (what kind of breadcrumb, what have you put in the titles and paths fields, etc), and what custom breadcrumb settings you have enabled at the /admin/settings/custom-breadcrumbs.
It would also help if you could share more about the view. It the view type 'node' or 'term' ? Is it a single view with multiple page displays? attachments? etc.
Comment #2
Standard Machine commentedI found out a bit more about this.
Data from the view are ending up in the breadcrumb. The first item from the view has its parent term being listed in the breadcrumb for all views.
This is for all the page-views being used.
Breadcrumb: Home > State > Region
Structure: home/state
Breadcrumb: Home > State > Region
Structure: home/state/region
Breadcrumb: Home > State > Region
Structure: home/state/region/subregion
Comment #3
Standard Machine commentedThanks for the response.
Its a single node-view with multiple page views.
These settings on the custom breadcrumbs configuration that are checked:
- Use the taxonomy hierarchy to set the breadcrumb trail for nodes and taxonomy pages
- Show current taxonomy term in breadcrumb trail?
- Use taxonomy breadcrumbs for views?
Including the story node type.
I am using the taxonomy module rewrite each of the terms that make up the breadcrumb trail. But I am not using the views module directly, just the check box through the configuration page.
Thanks again.
Comment #4
MGN commentedThanks. I think this is really a problem of correctly choosing the breadcrumb for a view with many displays, when each display has the same base path. Previously we wanted to ensure that arguments did not have to be explicit, so breadcrumb matches were allowed when the base paths matched. Here I suspect you are using display paths with explicit wildcard arguments (like home/state/%/%). In this case, we don't want to settle for a match on home/state or home/state/% if there is a valid custom breadcrumb on the display path home/state/%/%.
Can you try the attached patch and see if it fixes the problem that you are seeing?
Comment #5
MGN commentedOoops, I was working from the wrong version. Here's a patch against the latest dev.
Comment #6
MGN commentedFixing the status again.
Comment #7
MGN commentedI've found other issues in custom_breadcrumbs_taxonomy that also need to be fixed. I am working on it....
Comment #8
MGN commentedI've committed the patch in #5 and additional modifications of custom breadcrumbs for taxonomy that should fix this problem. See http://drupal.org/cvs?commit=267688 for details. Its in cvs now and will be available in the nightly dev snapshot. Feel free to reopen if you still see this problem in the latest code.