I have installed the GSA module into my Drupal 6 environment. I configured the settings required for the search and see that the hook for search is in fact working. When I make a query that returns no results, I get a message saying that the query found nothing. This is correct and I can verify it went to the Google Mini by running a report for searches that produced no results. If I run a query that should in fact return results, I get the words "Search Results" displayed, but with no content. Checking the reports on the Google Mini again, I can see that the query executed. It appears that the content I am getting back from the Google Mini is not proper or correct because it is not being displayed. I feel like things are so close to working on this and would love to see it in action. Could someone help me figure out whats going wrong? I have looked at the code, but its difficult to follow once you get to the results area.

PS - Why is the Drupal 6 version shown by default on the releases? I ended up overlooking it and ported it over myself (still had the same problem I am having now) to only find that someone had already did it.

Comments

Mark Theunissen’s picture

I can help you debug.

Take a look at function google_appliance_search(). In case 'search' it actually performs the search and delivers the results. A problem that I came across once was that the $results array (returned on line 317) was not formatted correctly according to the API reference for hook_search():

http://api.drupal.org/api/function/hook_search

So check to make sure that it's right according to spec. Check that other modules return results in a similar format when they implement hook_search.

Maybe the $results are not being populated at all? I see it calls this function theme_google_appliance_search_result_array($result) to actually theme the result. Is it working properly? If you var_dump() in there, what do you see?

Mark Theunissen’s picture

I have turned on the 6.x release display. Sorry, didn't realise it wasn't there as I never really look at the project page, rather just go straight to the issue queue.

brandon.dixon’s picture

This issue can be closed out. I had my old existing google appliance module in the same directory, but with a suffix added on to it. Apparently that was still being used by drupal even though it had a different name. Everything appears to work correctly now.

Mark Theunissen’s picture

Status: Active » Closed (fixed)

Great!