Add locations in Synchronize translations
zedzed - April 7, 2009 - 13:14
| Project: | Internationalization |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
Just add locations synchronization when translate content.
In i18sync.module on line 400 :
if (module_exists('location')) {
$options['locations'] = t('Location settings');
}that works perfectly.
#1
Subscribing, does this module translate location fields like country also?
greetings,
Martijn
#2
Not translate location, just synchronize.
If you add this code, a new option is in content management. When you edit content type, new option "Location settings" is in Workflow settings >Synchronize translations.
If you check this, locations informations are synchronized between translated node.
In fact, just copy $node->locations information.
i18sync already synchronize data from other module (i18nsync.module line 393) :
if (module_exists('comment')) {$options['comment'] = t('Comment settings');
}
if (module_exists('upload')) {
$options['files'] = t('File attachments');
}
always, sorry for my english ... i hope you understand me...
Seb
#3
This works great. Attached is the 5.x patch file. I'd mark it RTBC except I'm attaching a 5.x patch and the issue version is 6.x. Someone should attach a patch for 6.x and mark the status RTBC.
#4
Added the location field to 6.x, so re-tagging this one for 5.x
Thanks.
About the 5.x version, that one is on maintenance mode, no new features planned (Unless someone wants to take care of that branch and wants to test and commit these small patches there..)
However, I'd strongly encourage everybody to upgrade to 6.x
#5
@Jose Reyero
i use the newest 6.x release and the code you mentioned is included in the i18sync.module
but I can't see any setting for location in the "synchronise translations" sections for the contenttype
and lon/lat are not synchronised into translations?
any idea?
regards tom
#6
I think I've just fixed the issue
Not for 5.x anymore, no new features for that version.
#7
Automatically closed -- issue fixed for 2 weeks with no activity.