Synchronizing translatable nodes
on
May 12, 2009
Synchronizing translatable nodes
I just discovered the i18nsync module today. I'll be using this on every i18n site I develop. The only thing I found missing was locations, which was a simple patch.
i18nsync solves a horrendous problem, mainly that we're translating nodes instead of fields. Not all fields in a node need to be translated, i.e., images, numeric values, locations, user and node references, and taxonomies. (Small caveat... actually, we do need to translate the text of the taxonomy, but we should maintain the selection through all translations.)
i18nsync is bundled with i18n. In 5.x it's in the "experimental" directory, but in 6.x it looks to be just another i18n module. A little CVS snooping, and I discover, my old friend alex_b is responsible. Thanks! You just saved me a days work, and helped me get rid of a bad headache.
I used i18n and i18nsync on Rare Planet, which has almost been a full time job for me for the last 6-9 months, The site has significant improvements around og and translations, which will be the focus of several more blogs, and hopefully a DrupalCon Paris presentation.
sharon price (not verified) May 12, 2009
this is very interesting to see the power of open source communities in action --- so glad there is an available sync patch. can't wait to see how it works!
rareplanet is extremely challenging, as you know quite well doug. we are attempting to foster collaboration, across 4 languages, that will result in replicable solutions to common conservation challenges around the world.
thank you for your leadership on figuring this out!
sharon price
manager, global alumni network, rare
rareplanet.org
// Fields to be synchronized for mynodetype.// Remember we cannot use t() here, not loaded yet
$conf['i18nsync_fields_node_mynodetype'] = array('location' => 'Location settings');