Active
Project:
Context
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
5 Feb 2012 at 04:24 UTC
Updated:
5 Nov 2012 at 19:48 UTC
Jump to comment: Most recent
I have created a context with a "Taxonomy term" condition set to the vocabulary I want the reaction "Blocks" to display a block on the taxonomy term page, "taxonomy/term/myterm". However it seems that the "Taxonomy term" condition is never checked or called in code to check.
Not sure whats going on here but for the immediate time I have set the a path condition instead.
| Comment | File | Size | Author |
|---|---|---|---|
| noshowsblockfortaxonomy.png | 53.4 KB | dialn |
Comments
Comment #1
marco_cruz commentedSame problem here...
Comment #2
kortas87 commentedyou should use 7.x-3.x-dev (2012-Feb-03). I think there was problem with getting node terms in context_condition_node_taxonomy.inc
not working (7.x-3.0-beta2 2011-Sep-09)
WORKING (7.x-3.x-dev 2012-Feb-03)
Comment #3
benshell commentedThe taxonomy term condition is still broken in 7.x-3.x-dev 2012-Apr-02. The execute method in context_condition_taxonomy_term is never even run. Kortas87, I think you're referring to the Taxonomy condition, rather than the Taxonomy Term condition. I haven't tested to see whether or not that works now in dev, but I assume it does because I see the code you mentioned has been fixed.
Comment #4
Anonymous (not verified) commentedThe screenshot shows a "Taxonomy" condition, not "Taxonomy term".
You maybe missunderstand these two conditions. I'm actually here, because I think I made the same mistake and thought the "Taxonomy" condition would react on taxonomy term pages, but it doesn't - by design!
I've tested both types of conditions and can verify they are working well in 7.x-3.0-dev. So I'm setting the issue status to "works as designed".
Feature request posted: #1553012: Taxonomy term condition should allow for matching on term-level
Comment #5
samireez commentedI have been trying to show a block via context if a given node has a taxonomy term X. I was using the Taxonomy condition ("Set this context when viewing a node with the selected taxonomy terms.") but the condition would not successfully run. I have Context 7.x-3.0-beta2
I would like to confirm that the code outlined by kortas87 in #2 above works fine. I've only edited the plugins/context_condition_node_taxonomy.inc (inside the execute function). Once the edit is in place, the context seems to be working fine - even when a node has more then one term in a given vocabulary, context seems to match the condition properly.
Comment #6
steinmb commentedNew title, moving to feature req. We are able to tag terms with terms from other vocabulary so this should work with other entities then nodes. +1 from me to get this into context.
Comment #7
hixster commentedIs there any news on this? The ability to derive context on taxonomy term pages and not just nodes is crucial for large taxonomy based projects.