Doesn't seem to be a preferred way to include a set of nodes when translation is turned on. You're stuck with URL, which I always try to avoid.

Would love to use a list of path conditions like...

node/1234
node/2345
node/3456

... and check a box with the option "Include Node Translations"

CommentFileSizeAuthor
#5 context-condition_nid-1668832-5.patch4.15 KBdoublejosh
#4 context-condition_nid-1668832-4.patch3.62 KBdoublejosh
#3 context-condition_nid-1668832-3.patch0 bytesdoublejosh
#2 context_condition_purenid.zip4.74 KBdoublejosh
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

candelas’s picture

candelas CreditAttribution: candelas commented

subscribing

doublejosh’s picture

doublejosh CreditAttribution: doublejosh commented
FileSize
context_condition_purenid.zip4.74 KB

We implemented this via a custom module, which includes other context extras. Broke that off here for others to use.

doublejosh’s picture

doublejosh CreditAttribution: doublejosh commented
Status: Active » Needs review
FileSize
context-condition_nid-1668832-3.patch0 bytes

Here's a patch against Context core to add this condition.

doublejosh’s picture

doublejosh CreditAttribution: doublejosh commented
FileSize
context-condition_nid-1668832-4.patch3.62 KB

Whops. Empty patch. Here it is again.

doublejosh’s picture

doublejosh CreditAttribution: doublejosh commented
FileSize
context-condition_nid-1668832-5.patch4.15 KB

One more. This actually includes the trigger.