Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I needed this and I wonder why this simple addition was never added either to drupal core or this module, but I think it's worth considering.
Will follow a patch for review, hopefully this may get accepted.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | 837830-10-node-operations-set-language.patch | 900 bytes | hanoii |
| #1 | 837830_i18n-node-operations.patch | 881 bytes | hanoii |
Comments
Comment #1
hanoiiComment #2
mediamash commentedvery handy when imported nodes in the wrong language!
Comment #3
AdrianB commentedSubscribing.
Comment #4
brei9000 commentedI get an "Parse error: syntax error, unexpected T_VARIABLE" error with this patch... looking into the why right now...Edit: My typo. Patched worked fantastically! Thank you!
Comment #5
pyxio commentedI applied this patch but I can't find where to execute the process of updating node languages? How do I do that? Thanks!
Comment #6
hanoiiOn the Administer->Content Managment->Content page (admin/content/node), like any other mass node operation.
Comment #7
YK85 commentedsubscribing
Comment #8
1661Design commentedWill this be included in D7 ?
Subscribing
Comment #9
jose reyero commentedNo new features for 6.x.
Comment #10
hanoiiOk, what about for D7 then :)?
Comment #11
hanoiiComment #12
jose reyero commentedFor D7 it may be considered. Some issues:
- The patch implements hook_node_operations() for 'i18n', not for 'i18n_node' as I think it pretends.
- The node language in D7 has changed quite a bit and I am not sure what is the impact in field languages, whether we should change field languages too or not, what happens for ET nodes, etc..
- Node language list using i18n_node depends on node type (it may add disabled languages too, neutral may be allowed or not, etc.. So we'd need to check that before changing the node language for not creating inconsistencies.
For all this reasons, though I'd like to have this feature, I have some concerns about getting it in i18n_node, which is focused on some other API tweaks more than in high lever content features. I think it may be better as a stand alone module, that can fit in i18n_contrib if you don't want to create a new module. See http://drupal.org/project/i18n_contrib
Naming suggestions: i18n_content, i18n_node_translation, ....
Comment #13
jose reyero commentedA few months later, new features are really not wanted anymore. You can try a stand alone module or an addition for i18n_contrib.