After installing UUID and node_export via drush, I get the following error:

"Additional uncaught exception thrown while handling exception.

Original

SearchApiException: Unknown or invalid item type node. in search_api_get_datasource_controller() (line 1319 of /Applications/XAMPP/xamppfiles/htdocs//trunk/sites/all/modules/search_api/search_api.module).

Additional

SearchApiException: Unknown or invalid item type node. in search_api_get_datasource_controller() (line 1319 of /Applications/XAMPP/xamppfiles/htdocs//trunk/sites/all/modules/search_api/search_api.module)."

The site is now completely unreachable.

I've disabled the UUID and node_export modules in the system table and have removed them from the source tree. I've also (in an attempt to get the site back up) disabled the search_api modules in the system table and cleared the site cache using drush but the errors still persist (!)

I've tried the patches suggested for overcoming this issue and have updated the search_api module to the latest release but to no avail.

Is this an issue with search_api or am I doing something wrong? (entirely likely)

Comments

WoozyDuck’s picture

WoozyDuck commented

Same issue here !

dits’s picture

dits commented

Experiencing exactly the same. No UUID module.

sorgo’s picture

sorgo commented

I can confirm the same after installing node_export and uuid. I am using fuzzysearch.

fboes’s picture

fboes commented

Confirming cause of error to be UUID module. Latest dev version of UUID module fixes this issue for me, but I need someone to confirm that this is a general fix. :)

codesidekick’s picture

codesidekick commented

Can confirm installing UUID also brought down a site for me, couldn't reset it so had to restore from database backup. No errors in the error log - just the error in drush

Unknown or invalid item type node. in search_api_get_datasource_controller()

vuzzbox’s picture

vuzzbox commented

I was getting the same errors when attempting to enable a feature. The feature imports a content type *and* nodes of that type, using node_export, I believe.

The Feature enablement did not complete. Same WSOD, same errors in log file, same disabled site, same drush results as discussed above.

I was using: search_api 7.x-1.2 and uuid 7.x-1.0-alpha3.

I installed the UUID dev version (uuid-7.x-1.0-alpha3+51-dev) and that allowed me to get my site to come back up without restoring.

Here are the steps I took:

  • Deleted uuid folder from modules. Tried a simple drush cc all to see if I could get past the errors. Same error messages (not surprising).
  • Deleted search_api folder from modules. Ran drush cc all and got clean result. Site also came back online (but without search api, uuid and without my completed feature import).
  • Downloaded and enabled UUID 7.x-1.0-alpha3+51-dev (current dev version). Clean install, no errors.
  • Downloaded and re-eanbled Search API 7.x-1.2. Clean install, no errors.
  • Ran drush cc all again. No Search API errors, site back online.

Surprisingly, (as an aside) the features node import finished up when I ran the drush cc all command (I guess it queues those actions up somewhere? Or maybe that was just a system message from the original feature enabling that was waiting in the wings?)

emjayess’s picture

emjayess commented

Same scenario as #6, and updating UUID to -dev helped to recover the site. BUT then enabling commerce_search_api causes it to explode in the same way again, with exactly the same error, originating in search_api.module line 1319.

Myoos’s picture

Myoos commented

I had the same problem and I can confirm that #4 solved or removed the error =)
so thank u so much

spypolo’s picture

spypolo commented

I have the same problem.
I use features and node export in a kickstart distribution.
I reported a bug here http://drupal.org/node/1902876

smussbach’s picture

smussbach commented

The issue isn't fixed in current uuid 7.x-1.0-alpha3 released on January 31. You still have to use solution in #6 & #4 with current dev

kubrt’s picture

kubrt commented

Same here, #6, then also hit Unknown column 'base.uuid' http://drupal.org/node/1255550

liza’s picture

liza commented

I CAN CONFIRM THIS BUG happened every time i try to clear caches thru Drupal UI. followed instructions in comment #6 but substituted SEARCH API for the latest DEV. now the site can clear cache with no problems.

drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
commented
Title: SearchApiException: Unknown or invalid item type node. in search_api_get_datasource_controller() » Using UUID with this module makes site unusable
Category: bug » support
Status: Active » Fixed

Reading #1902876: Enabling UUID (Universally Unique ID) module causes SearchApiException: Unknown or invalid item type node. and #1663390: Roll a new UUID stable release, I think it's pretty clear this is a (very serious) issue of the UUID module. I'm closing this one therefore – please go to #1663390: Roll a new UUID stable release and help pleading with the UUID maintainers that they do a new release.

Status: Fixed » Closed (fixed)

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