Active
Project:
Location
Version:
7.x-3.x-dev
Component:
Location_views
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
28 Mar 2009 at 20:56 UTC
Updated:
6 Sep 2018 at 17:13 UTC
Jump to comment: Most recent
Comments
Comment #1
andrewsuth commentedAfter some more reading, I found this discussion regarding Italian regions (NUTS level 2) and provinces (NUTS level 3): http://drupal.org/node/183580
While I agree with this to an extent, it does seem strange for a user to complete the fields like this:
Perhaps a better solution would be to include NUTS level 2 and NUTS level 3 into the list for Italy? For example:
Like this we can maintain the province codes ("MI" for "Milan, Lombardy") and include more information for the users. While Italians think more in NUTS level 3, foreigners think of NUTS level 2. My example above would cover both circumstances.
What does everyone else think of this?
Comment #2
yesct commentedDo you have any idea what data file, or code would have to change to implement this? would this be a location.xx.inc thing but for Italy?
Comment #3
pescetti commentedI find perfectly normal to write
and province names, not region names, are what you would use for addressing a letter. So I wouldn't change this behavior.
Comment #4
andrewsuth commented@YesCT: Alterations would need to be made in the files associated to the regions of the country. For example, to change Italy it would be necessary to alter the
supported/location.itfile.From:
'BO' => "Bologna",To:
'BO' => "Bologna, Emilia-Romagna",@pescetti: You live in Italy and have proven my point exactly. As I said before: While Italians think more in NUTS level 3, foreigners think of NUTS level 2. My example above would cover both circumstances.
I think that most people in the US, UK, Australia, New Zealand would be confused by
Italy -> Bologna -> Bologna (city)We tend to think:
Italy -> Emilia-Romagna -> Bologna (city)Proposed solution: Perhaps there could be 2 files for countries like Italy in these circumstances: one in
supported/location.itand another insupported_alt/location.it? Then the use can choose which to use, and copy over the "alt" version to the directory if he chooses.Comment #5
vthirteen commentedsubscribing
Comment #6
juicytoo commentedlocation currently autocompletes
for "state/province",
it would be great if it did the same for "city"
and then populates the postcode field based on the zipcodes table via dropdown selection.
I'll like to contribute $20 towards this feature.
Comment #7
vthirteen commentedi'm Italian and i would not use province when addressing a letter but i would definitely need Regions (NUTS 2) as an additional variable to store, index and view my nodes.
Comment #8
yesct commentedtagging
Comment #9
yesct commentedIs there still interest in this?
Please confirm the problem in the new official release. Also, if the problem is still there, please set the status back to active. And, if it is still there, if more people pool their money, the bounty might draw more interest if the amount increase. Thanks.
Comment #10
kurageart commentedI'm italian, and I think too that Region is very important here...
Any update about it, or suggestion on how to implement it manually?
Thanks
Comment #11
windsurfitaly commentedso...there is a module that make this for me? i don't know hoe to put my hands in code pages! ...sorry :(
Comment #12
rooby commentedThis should go in the location.it.inc file in the supported directory.
If someone who knows about Italy's state/province system could do a patch to fix any problems it would be appreciated.
As for autocomplete cities, that is a completely separate thing and probably already has it's own issue.
Comment #13
openmode commentedI suggest these modules:
Location Region: /project/location_region
Location Views Filters Ajax: /project/location_views_filters_ajax
Even if I have some problems with JQuery 1.7 and Exposed Filters in Views.
When I try to add the provinces (location module) exposed filter in the top of a view , I view this message:
error HTTP in AJAX.
Code HTTP 500
Path: /admin/structure/views/ajax/config-item-extra/......view_name......../page/filter/province
StatusText: Service unavailable (with message)
ResponseText:
My configuration:
Views 7.x-3.20
Location 7.x-3.7
Location Views Filters Ajax 7.x-1.0
Clean URL Enabled
JQuery 1.7 (same error with 1.10)
https://www.drupal.org/project/views/issues/1376686
https://www.drupal.org/node/1183418
https://www.drupal.org/project/location_views/issues/118099
https://www.drupal.org/project/location/issues/330066
https://www.drupal.org/project/location/issues/2127933
Comment #14
damienmckennaPutting this back to a "bug report" because it refers to incorrect data coming from the popup.