Hey guys,
Struggling to get this working: I'm using node locations for locative data on my nodes. I'm using search API & the solr integration for search (hope to use facets, sorts, ranges, too someday!) But i'm getting stuck.

No matter what I do, I cannot get any locative data available as "relevant fields" - under - search api > default node index > fields

Now here is the kicker. I remember having some locative field options there at some point. But when I couldn't access them through views, I started trying different location modules. At that point things hit the wall, and now nothing shows up.

Goal is ultimately to be able to filter my nodes by state/ country with search api & solr integration using facets.

On one of these boards I found a location entity module, and i'm using that as well. Do I need to hook into entity for this?

Comments

raulmuroc’s picture

raulmuroc commented

Completly the same question. Since D6 I'm trying to find this functionality but nothing... :S IS curious that so basic conceptual thing as search by city and/or country through search box is so difficult to implement in Drupal.

Hope it would be something similiar putting together our efforts! ;)

Refineo’s picture

Refineo commented

@stopshinal, @RaulMuroc can you please confirm what versions of Location do you use ?

Location 7.x-4.x is an abandoned branch that was originally intended to implement locations as entities.

Can you please install the latest 7.x-3.x-dev module and the latest Drupal core and test again?

If you cannot find an answer here, you can also try to search on drupal.stackexchange.com

magicmirror’s picture

magicmirror commented

Same issue here. Did anybody on this thread ever find a resolution?

raulmuroc’s picture

raulmuroc commented
Version: 7.x-4.x-dev » 7.x-3.x-dev
Priority: Critical » Normal
Status: Active » Fixed

We are working on 7.x-3.x-dev.

Inside project Location: http://drupal.org/project/location must be used sub-module 'Location CCK'.

Not other way.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.