Location Module and Exposed Filters

Status: 
Open
Question: 

Hi all,

Anyone know how to get exposed filters to work for a view when using the location module? I have a view that list a location and I want to have an exposed filter block that searches by city and country. Problem is that the exposed filters are not working when you enter the city name or choose the country in question. I tried just exposing a location: city and location:country. I then tried to expose my content using field_example_location. Neither one works.

Responses

1. Does the view work without

Does the view work without the filters?

2. Nope

I had the views output the location in its entirety by adding the location content variable field (field_example_place) i.e. it outputs all the variables associated with location. If I try adding location:city or location:country as a field, the view displays nothing with or without the filter. So the problem must be with displaying or filtering just a city or country. What is the best way to correct this?

3. You need to select the

You need to select the appropriate values when you set the filter eg. Location:country all.

Or if you want them exposed, you need to check the exposed box.

4. Tried that, didn't seem to

Tried that, didn't seem to work. I have a field called field_job_location that is a location_cck field. I go to setup a table view in views and add a column for location:city and location:country. I have views filter only the content type associated with the location field I want i.e. field_job_location is under the content type created called "job" so filter for only "job". All other fields are displayed except for the location fields. I'm guessing that is why the exposed filters won't work either. Is there a relationship I need to declare to tell views to display location:city and location:country for the specific field? Keep in mind that I have other location_cck fields created for other content types like field_profile_location and field_school_location but field_job_location is associated only with the job content type.

5. Fixed (temporarily)

The problem is a bug with location_cck.module. Can't make a relationship for the location type. Same problem is discussed here:

http://drupal.org/node/427432

Fixed by installing the latest dev version of locations. Can make a relationship in that one.