Closed (outdated)
Project:
Location
Version:
6.x-3.0
Component:
Location_views
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 May 2010 at 09:00 UTC
Updated:
19 Jul 2016 at 12:16 UTC
Jump to comment: Most recent
Comments
Comment #1
hutch commentedIf the country you are working with does not have a province list in a function location_province_list_xx where xx is the country code then no lookup can be done. the file this function should be in is in the supported folder.
If the above is there then there might be a bug in handlers/location_handler_filter_location_province.inc. If you can try sticking some watchdog lines in to see if the data is being collected or not
BTW best to work with dev if you can, it really is much better.
Comment #2
raj47i commentedI am not very sure that is the problem-
In the node location add/edit page, the Province auto-complete works well.
And even in this view page, the auto-completion do come up (Probably not very correctly)
1st I have to select United States, the click apply so that the correct states come up - otherwise auto complete will be for some other states.
So, I believe location_province_list_xx functions are there- The problem should be where the Condition Queries are generated -
I have not had a chance to dig into the views architecture, so I dont know how is it structured !?
I cannot use dev, as this is for Production use.
Comment #3
yesct commentedYou can use dev... just test it on a copy of your site first before putting it on a live site. Then once you are sure it works, dont update dev again until you need a fix that might be in a new dev version.
Hopefully a new release will come out. But if this is fixed in the dev version, you wont see any movement on this issue (fixes are not being made against 3.0 at this time), and it will be considered fixed if dev works for it.
Please try the dev version on a test site, and report back if it fixes your problem. Thanks a lot for being patient while the new version is being worked on. If you can sponsor work to speed the release of a new version, please contact me.
Comment #4
John Carbone commentedI was working on something similar and ran into the same issue. My implementation is different, as I have an argumented View that filters by country, then on that page, you can filter by state. I attempted to fix the autocomplete version but abandoned it because the parameter in the URL wouldn't work. It sends the human name versus the two letter machine name for the state, which the query expects. Anwyay, here's my fix. Maybe it will help someone.
Comment #5
raj47i commentedthank you for your reply, This feature was not very crucial for my project so I completed it otherwise.
But I am sure, your fix will be useful to someone!
Comment #6
poorva commentedThis problem is still appearing in "6.x-3.x-dev" version and also recommended "6.x-3.1" version.
View expose filter with location province does not work.
Comment #7
poorva commentedCan anybody help me to resolve this issue.
Comment #8
selwynpolit commentedWe created a module to handle this. I thought it might be useful to share. The logic is:
1. build a list of provinces & countries that have been used so far.
2. Sort them and add an Any option
3. For my views form (the $form_id), change the provinces autocomplete form field to a select box and populate it with the list of provinces from above. In the code, I am using this for 3 different views.
4. For my views: when a selection is made, find the province field and fill it's 'where' clause value with the state/province selected and voila!
I hope this is useful for someone.
Comment #9
legolasboClosing old D6 issues as D6 is end of life