node taxonomy condition failing on translated or multilanguage site

Thanks for the fix. I'm building a single-language site (non-English) and was running into the same problem.

I just came across the same bug and fixed it, before i found this =).

i used field_get_items() instead -- which is the best way to do it?

#4 works well for me.

Hello.

A question. I need replace all code in context_condition_node_taxonomy.inc with the patch? or Add the patch to existing code? thanks

@antoniomanco
See http://drupal.org/patch/apply

field_get_items() is cleaner. Seems like this is the only case of incorrect field language usage in context.

#4 wasn't rolled correctly. Attaching a reroll and marking RTBC.

I can't seem to apply this this patch. Git apply -v simply returns no result / error / nothing and the file was not patched whatsoever. I downloaded the file to sites/all/modules/context and git apply it from there. The patch in #4 worked fine though.

patch -p1.

Tried as some suggested that git apply does not work from within the local checkout of an unrelated git repository. Didn't work as I hoped.

FYI I'm running Git 1.7.6.

Great, thanks for testing.

+++ b/plugins/context_condition_node_taxonomy.incundefined
@@ -51,8 +51,8 @@ class context_condition_node_taxonomy extends context_condition_node {
+        if ($terms = field_get_items('node', $node, $field)) {

This could be easier to read. I propose doing it like so:

$terms = field_get_items('node', $node, $field);
if (FALSE === $terms) {

I personally really dislike if assignment statements.

This is a version of the above patch from #8 to use in a make file.

Patch form #8 did not work for me.
But the original one from #1 was fine!

I am using dupal 7.10

Committed to 7.x-3.x with commit f5966dc5e3aea325802ea41e6ca26ba9ad90d2c0, will be available in next dev build. Thanks for the bug report and to those helping to roll a patch.

Patch in #4 worked, but it wasn't prepared for git patcher... I had to modify it.