Jump to:
| Project: | Panels |
| Version: | 7.x-3.2 |
| Component: | Views panes |
| Category: | support request |
| Priority: | major |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I have a panels page with a variant containing various contexts from taxonomy terms. I am passing those contexts into a views content pane display. The views display is accepting the contextual filter as a context of the type taxonomy-term:name.
The panes are placed into various regions on the panel layout. The panes that pass a taxonomy term context where the term name has no special characters work as expected. The panes that pass a taxonomy term context where the term name has an ampersand are breaking in Views. Views reports that the contextual filter is not present.
If I change the ampersand in the term title to the word 'and' then the view displays correctly.
My questions are:
1. Why is the term name being passed as a context rather than the TID?
2. Since it is the term name being passed, why are special characters breaking it?
3. Since it is the term name being passed, how does views know which term to load if multiple terms have the same name?
Comments
#1
See: #1768738: Terms with ampersand are not converted to term-id when sent as arguments
#2
No patch attached. This should not be 'needs review'.
#3
The question of "Why it's passing a term name instead of a tid" is answered by "Because you configured it that way." When passing a context to Views, YOU select which aspect of that context to give to Views. You must have selected the term name; however, a tid is the better choice.
The rest of it probably has to do with tokens trying to make the output safe, something that was fixed not too long ago in the CTools views_content module.
#4
Automatically closed -- issue fixed for 2 weeks with no activity.