By maozet on

Hey,

I have a content type 'Store', which has title, opening hours, images, location...etc. After creating a store node i then wish to translate it.
Every thing is fine except with location & GMap modules fields
All other fields (title, images, opening hours (date module)) are auto filled with the previous language info i have just created.

How can auto fill GMap + Location fields as well? (Fax, Cordinates, Phone...etc)
If i need to hack those modules, can anyone point me?

Regards,

⋅ Categories: Drupal 6.x

Comments

Eric B.’s picture

Eric B. commented

I have the exact same issue. Were you able to resolve this?

Thanks,
Erica

distanceroller’s picture

distanceroller commented

Any help is very welcome!

Thanks,

FranK

suffering drupal’s picture

suffering drupal commented

I posted this same problem some 2 years ago too. And have not got any answer.

We have a tourism site in 6 languages with lots of landmarks, hotels etc.... To start with, we did not want to loose time in repeating 6 times the same info for the map. Neither did we want to fill the database with redundant information (6 times the same map...).
I thought it was ridiculous that for a supposed multilanguage focussed system like Drupal (not always true) the guys who developed map don't even seem to have bothered to integrate this in their module. More ridiculous now, two years later, they still haven't come up with any solution. In fact many times they don't even reply to these kind of posts (http://drupal.org/project/issues/gmap - in fact gmap maintanance status is unknow...).

In our case we solved it through a work-around making a map-type node and having the content-type refering to it. It's rather a hassle and a friend did it for me so I can't explain much more. It avoids duplication of work and of needless dates in the DB, but it's a bit clumsy from the user input side: 2 steps and in the content type you have to select the map from an ever increasing list of available maps. Always, also in translations (unless of course you know how to program that automagically, but then you could do the same directly for this missing quality of Gmaps itself).
Problem here is that it seems to use more memory and need more loading time. I'm not sure, but it seems the reason for which our belgian drupalspecial host decided to just kill our site without further notice... :(

In case of someone wanting and being able to make the patch or the hack:
easiest, I suppose, would be to just overwrite the fields for the translations with the exisiting dates from the source language. But then you still are producing redundant map information. Besides, if you want to adapt a location you have to remember to do it for each of the translations.

I am sure the reference of the source-node could be used here to link to this only one map per language.
Who knows, maybe within some 4 years some contributer hears us screaming in the desert.

I started with Drupal in 2007 and then my life got stuck...