I used a custom script for importing nodes into Drupal using raw database queries. Everything was working fine in Drupal, but the "Guided search" block didn't show up. Rebuilding taxonomy facets (which amounts to running cron) didn't help.

After some debugging it turned out that the problem was missing entries in database table `taxonomy_facets_node`. These entries were missing because my custom import script wasn't inserting such rows.

Solution was to disable and re-enable "Taxonomy Facets" module and subsequently running cron.php.

Suggestion for improvement of "Taxonomy Facets" module:
Modify taxonomy_facets_cron() so it fixes for missing entries in `taxonomy_facets_node` like in taxonomy_facets_enable(). That way errors in table `taxonomy_facets_node` will automatically be corrected at each cron run.

Comments

brynbellomy’s picture

brynbellomy CreditAttribution: brynbellomy commented

subscribe

k3n3dy’s picture

k3n3dy CreditAttribution: k3n3dy commented

subscribing.
The same happens here when importing data using Node Import 1.0-rc4. What's weird is that it used to work ok, having imported lots of content. After migrating site from dev to production I was able to do three successful imports, then the next one didn't work. Tried manually updating taxonomy_facets_node, rebuild index, run cron, but nothing helped.

appmux’s picture

appmux CreditAttribution: appmux commented

Make sure the database user has privileges: LOCK TABLES and CREATE TEMPORARY TABLES.

noocx’s picture

noocx CreditAttribution: noocx commented

If you mass update the relevant items(as a temp solution), the _taxonomy_facets_update() gets called and it (re)creates those missing rows. On some day ill write a patch if no one does:D First need to find the reason what causes this.