If you go to http://example.com/search the core search module will redirect the visitor to http://example.com/search/node and provide an error:
Fatal error: require_once() [function.require]: Failed opening required '/search.pages.inc' (include_path='.:sites/all/modules/luceneapi/lib:/Applications/MAMP/bin/php5.2/lib/php') in includes/menu.inc on line 346

Comments

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

Quick follow-up, the next page load displays the following error:
warning: require_once(/search.pages.inc) [function.require-once]: failed to open stream: No such file or directory in includes/menu.inc on line 346.

cpliakas’s picture

cpliakas commented
Category: feature » bug
Issue tags: +6.x-2.5

Hi Damien.

First, make sure you look at the "Hijack search box" setting, in admin/settings/luceneapi, because this is where you can make Search Lucene Content the default search. In terms of the error, this occurs when you check the "Hide core search" options in admin/settings/luceneapi_node/general but leave the "Hijack search box" setting in admin/settings/luceneapi to "No". The problem is that the core search tab is hidden, but searches are still going to the core search.

Marking this as a bug report because the user should never be allowed to configure themselves into a hole. There should be some validation that is performed that makes sure a Search Lucene API search is set to be hijacked if the "Hide core search" button is selected. Let me know what you think about this approach.

Thanks,
Chris

brazorf’s picture

brazorf commented

I think i found out what happened, at least in my case. This issue showed itself when i did disable the "Hijack" feature.

That was because i installed Lucene api AND Lucene content. Now, Lucene content has another option :"Hide core search". If you do hide core search, and do *not* hijack the search requests(by unselecting the option), the module goes little crazy. I didnt dig in with debug, but unselect that option did the trick for me.

bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
commented

This is interesting. I noticed something strange when in the "Navigation" block for the superadmin, there was a bulleted link with no text in it. I looked at the source and saw an empty link to "/search/node". Going to that path as super admin resulted in the same error as OP. If I go to that path as anyone else, I simply get an accessed denied page.

I have my Lucine settings to hide core search and to hijack it with this module. What could be causing that link to appear blank in my Navigation block?

cpliakas’s picture

cpliakas commented
Status: Active » Closed (won't fix)

Due to the end of life announcement, this isn't going to get fixed.