Hi,
I have a vocabulary called "Blog topics". "Blog topics" terms are common to all languages so they are i18n localized.
I set up a condition of type Taxonomy Term and I checked "Blog topics"
I set up a reaction of type Blocks and I added a few blocks on my sidebar second.
The blocks appear when I visited the term's page in the source language but not when I visit it in a localized language.
Let me know if you need more info to reproduce the bug !
Bye
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | context-localized_taxonomy_term_page-1815682.patch | 688 bytes | h3rj4n |
Comments
Comment #1
ykyuen commentedI am having exactly the same problem with 7.x-3.0-beta6.
Comment #2
nicolas bouteille commentedWhat I did personally in the mean time is set up a condition of type Path on "blog/*" and "blogue/*" instead.
Comment #3
h3rj4n commentedIt took some time to figure this out but the problem lays in the following:
The context is only attached when the $term object meets the menu_get_object value. In my case the menu_get_object function returns the following:


This will be compared with:
As you can see the term object that is provided to the hook contains the translated name. The object fetched with menu_get_object is not translated. I would suggest not to check on the entire object, but only on the term id. The code is only executed on the taxonomy entity so the ID should be unique for this entity.
I applied a patch to add this to the context module.
Comment #4
h3rj4n commentedForgot to set it to 'needs review'
Comment #5
tekante commentedCommitted with commit 16aa5aeed85626b3f189316ef2717f6a2d982d15. Thanks for the bug report and patch.