Closed (fixed)
Project:
Apache Solr Search
Version:
6.x-1.3
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
21 Jan 2010 at 21:03 UTC
Updated:
18 Jan 2012 at 15:48 UTC
Hi I just installed this module after noticing the good work its in in drupal.org but now I get this I cant even see user profiles. someone help please...
Fatal error: Call to undefined function apachesolr_get_nodes_to_index() in /{path}/sites/all/modules/apachesolr/apachesolr_search.module on line 94
Comments
Comment #1
pwolanin commentedThis is the only report of this - check that you got all the module files. Did you move the module files after installing?
Comment #2
johnlinux commentedno I didnt move anything. I just installed normally. extracted the tar ball, then moved it to the sites/all/modules directory, then enabled it on the modules page. anything else that im supposed to do other than that?
Comment #3
pwolanin commentedComment #4
foredoc commentedAny solutions? I got exactly the same problem here.
Comment #5
cjdavis commentedSeeing the exact same error here. The really strange part is that it is working fine on a separate site copy running on the same machine so 99% of the site is identical, including the environment. And it continues even after copying the apachesolr code directory from the functioning copy.
I can confirm the apachesolr_get_nodes_to_index() function is present in apachesolr.module.
Comment #6
cjdavis commentedComment #7
cjdavis commentedIt turns out that I somehow had the apachesolr_search module enabled, but not the apachesolr module. The dependencies are there, so it looks like something glitched during installation. Disabling / enabling everything fixed it.
Comment #9
Toktik commentedSame problem as described cjdavis.
ApacheSolr enabled but Framework module is not enabled. Maybe caused by missing SolrPhpClient while installation?
Comment #10
mcaden commentedconfirmed, I had the same problem toktik had. I disabled and re-enabled and it worked fine.
Comment #11
pwolanin commentedComment #13
fonant commentedI had this, I think because I switched from the 7.x-1.x-dev version to a 7.x-1.0-beta version. Easily fixed by uninstalling all apachesolr modules, deleting any remaining tables, and re-installing.