Many times added the same country, State, locality if using many languages about django-address HOT 6 OPEN

Same here. Looks like a design issue, language is not even part of the data model :(

This leads to too many and wrong results in value helps.

There was an attempt to repair (lookup comments for something like 'duplicate key issue with key IT

from django-address.

...(enter /comment-end unintended)
') that prevents crashes with duplicate keys, but adds a data consistency problem because unawareness of different results from Google Maps with different languages set.
I don't see a solution other than a major redesign of underlying tables.

from django-address.

Hi @hisie, are you using the dev or master branch?
The master branch was designed around Australian address structure, the dev branch was a rebuild which works with multiple objects, and as such works very differently.

from django-address.

@bendog Thanks for fielding questions! @hisie Yeah, clearly I've not given this project the attention it needs, my apologies. As @bendog says, the master branch was written specifically with Australian addressing in mind. The dev branch was an attempt to make the system more global, and involves leveraging a more general structre from Google's geocoding system. This change gives a lot more internationalisation support, but makes the software much more complicated.

from django-address.

I've Added a note to the model architecture update notes about this issue here.

I believe that the javascript geocoder plugin needs to be configurable to a single browser's language. That way if you have users entering data from multiple language settings the same response should be received from Google Maps.

I've added this to a new milestone, Future Features, for now.

from django-address.

@banagale
Im also running into an issue with Spanish users adding their address in the Spanish language. I have to change it to English manually in the admin every time.
Any indication when this can be picked up?

from django-address.