I really hope this isn't a duplicate issue. I wasn't able to find anything in the issue queue. I've recently made the change from Apache Solr Integration to Search API coupled with the Search API Database Search module. (the "it's good enough for Drupal.com" comment sold me alone) Before implementing Search API with Search API Database Search, I had "Node" available for the ItemType dropdown for creating an Index, and the search page also reflected "Node" and "User." Now Node is replaced with the term Content in a couple of places, as I'll explain. Additionally, Node is still set as the default and active search module, and facets now do not work.

I have Drupal Commerce module, Search API, Search API Database Search (7.x-1.5), Faceted Search (7.x-1.5), and Display Suite Search (7.x-1.5) installed. The dropdown for the ItemType displays Commerce options along with Content instead of Node. Facets of any sort refuse to display, whereas they were working ok before.

Facets do not display for commerce indexes either, and while that, on the surface, seems like it may be related to the commerce module's compatibility with Facet API, I think once I correct this issue it may lead me to correct the latter since the default Node term has gone away.

No watchdog messages either. I've also disabled all search modules aside from core Search, Search API, and Display Suite Search, reran Cron, and cleared caches, no luck. This seems like a configuration issue on my part, as this has only happened since enabling/disabling modules (changing from Solr) and I'm wondering if there are any known module conflicts that could cause this.

My final (but initial) thought, if it's simply that module updates have changed the term Node to Content (my pages are indexed still but on the other-hand, maybe this is part of the Node module simply functioning as it should when I cron?), where should I move this issue, Facet API? (I brought the issue here after disabling other modules)

(this seems related to some other threads, however, it seems those threads are issuing Commerce Search as the culprit which I don't have installed. I did at one point install Apachesolr Commerce to attempt to get facets working with my previous search setup, but it is now disabled and Node was still a search page tab, not Content.)

Any thoughts?

Comments

SmallAnvil created an issue. See original summary.

drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
CreditAttribution: drunken monkey as a volunteer commented
Category: Bug report » Support request
Status: Active » Fixed

Please see the "Getting started" section of the Search API handbook. The most important thing: Search API does not integrate with the Core "Search" module, it's completely independent of it. That means, unless you have a specific need for it, you should disable the normal "Search" module if you're using Search API. (Same for "Faceted Search" and, I guess, "Display Suite Search" – I don't even know the latter.)

For your use case, probably enable:
- search_api
- search_api_views
- search_api_db
- facetapi
- search_api_facetapi

Then follow the steps from the handbook to create a search index and search server (the former is already there, though) and then a view using the index.

Status: Fixed » Closed (fixed)

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