Conditions = Taxonomy - No Reactions

I've been digging into the D7 translation system a bit, and have a couple questions regarding what you are trying to accomplish and how your site is configured so I can set up a similar testbed:

• Are you using D7 core localization only, or also the i18n module?
• Are you translating content using multiple nodes, or entity translation (one node, each field is translated)?
• When you are setting up the context, it sounds like you are adding a Taxonomy condition and selecting value(s) to trigger on, then setting the reaction to show blocks in certain regions based on the condition. Is this correct?

The reason I ask is I enabled D7 core localization and i18n, enabled a content type for translation, and created an English node, then the Spanish and French translations of that node for a complete translation set. All were tagged with the same vocabulary term (in this case the term 'drupal' that I added to the core Tags vocabulary). I was not using any form of taxonomy translation for this test.

When I enabled a context and added a Condition for Taxonomy where the tag was 'drupal' and enabled a block to show in the footer region, it works for all nodes in the translation set (English, Spanish and French). If I remove the tag from one of the translation nodes (i.e. Spanish), it does not show the block for that node but still shows it for the others (English and French).

I am testing against the 7.x-3.x branch right out of the project repository, so wonder if this might have already been fixed in the dev branch of the code... Could you please let me know if your translation configuration is different from what I tested?

Thanks!

I had a similar issue with no reactions for various content types with the same taxonomy term.

Example:

content type: category-page
content type: product
both had corresponding content with the same taxonomy term: laboratory

Context Setting

I set context to react on these content type when the taxonomy term laboratory was tagged on content of those content types.

Language

I did not have the i18n module installed but on Drupal 7 the language English was set under regional settings.

• The category-page content type did have language translation enabled and the content of that content type was set to language neutral
• The product content type no language translation was enabled

Result

I found that even though there was no setting in the context that referenced language:

• for the category-page content the context reaction was working
• for the product content-type the context reaction did not work

Check

I found that when I enabled the language translation for the product content type and assigned the content to be language neutral that the context reaction did work.

Double Check

I tested on another content type and found the same result.

I hope this helps someone.

@guysaban - thanks for the detailed setup info. I'll take a crack at that this evening and see if I can replicate it.

The problem is in menu_link_get_preferred in menu.inc

menu_names should be ordered so that menus with current language comes first.