-
-
Notifications
You must be signed in to change notification settings - Fork 857
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cities did not pull to correct states #749
Comments
Which Odoo version? |
Odoo 12, CE |
any other thoughts on this @pedrobaeza ? |
Not right now. I'll check next week when coming from holidays |
Hi Pedro... Any updates on this? I need to build up my production server and I'm concerned this bug will follow me there and I'd like it if it doesn't. Thanks! |
For what it's worth, I just spun up a completely new instance of Odoo 12 CE - installed the addon/extra and it did the same exact thing. Ubuntu Server 18.04 x64 with Odoo 12 CE. All up to date with latest patches/updates/etc. |
I come back from holidays tomorrow, and I'll need sometime to find the problem. |
So sorry to pester, but I'm trying to go live with this and I was wondering if there's been any headway on this. |
@pedrobaeza - Is there any update on this? I'm sorry to continue to pester, but without this working properly I'm kind of stuck with setting up my production database, as I don't want to manually input data if it will disrupt your/our troubleshooting in any way... |
Sorry but no. This is not top priority for me, and although I confirm there's a bug, I need some free time for checking and solving. I will try this week. |
Hi Pedro, Any luck on a fix for this yet? Has it always been broken or is there something unique about how it runs now that causes it to break? Thanks- |
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
You can find the fix in #757 |
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
If there are several cities with the same name in different states, previous code doesn't handle correctly this situation. We amend this storing in the cached dictionary both city name and state. Includes a test for checking this specific condition, got from real data in US. Fixes OCA#749
Hi there,
I did my first import from geonames just yesterday and I'm noticing today that many of the cities that have the same name in multiple states did not get imported correctly. For example, Worcester, the city, resides in MA, NY, PA, and VT. But upon import, it's placed ALL cities named Worcester into VT. (see screenshots for a few examples)...
The text was updated successfully, but these errors were encountered: