Posted by vosechu on May 19, 2010 at 6:01pm
| Project: | Context |
| Version: | 6.x-3.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Issue Summary
Rolled against current HEAD but I couldn't select that in the version dropdown.
We have a site which wants to display blocks or change the CSS of all pages that are translations of some other node in a consistent way. Rather than adding the paths to all the child nodes I built a context plugin and I would love some feedback about whether this is worth including and how I can improve it.
This is my first patch so please bear with me.
Steps to try it out:
Enable i18n
Create a node
Create a translation of that node
Create a context and select the title of the translatable node under the Translations condition
Add some reactions
See if they worked on the child nodes
Comments
#1
Forgot to attach patch
#2
#3
I'm guessing things in the feature request queue basically get ignored unless they have a patch so I'm changing the title to try to get a little more traction. Thank you for adjusting my status grendzy.
#4
I'd like to consolidate all i18n-related issues and see if it's enough for a context_i18n contrib project or for pushing directly into i18n. Please see #773118: i18n integration and other workarounds.