this bit of the settings form, and corresponding documentation (README) is misleading...

API Key
Your Google Site Search API key. If no key is given, the module will not work and will be disabled.

should actually read:

Search engine unique ID
Your Search engine unique ID. If no ID is given, the module will not work and will be disabled.

the parameter you're sending in your http request is "cx" which is the google cse search engine id.
if your code Were sending api key (which, curiously, it does Not), that parameter is "key".

it took us a bit of head-scratching to realize what was going on and to successfully configure this module as a result.
please correct.

Comments

kris-o3’s picture

Issue summary: View changes

*edit*

janamills’s picture

+1 on this - though thankfully found your comment and avoided too much scratching. Thanks!

dhavyd’s picture

Status: Active » Fixed

Hi kris-03! Thanks for the comment. I've fixed and commited it. The change will appear in the next release...

dhavyd’s picture

Status: Fixed » Closed (fixed)

Released!

kancharlawar’s picture

Category: bug » support
Status: Closed (fixed) » Active

may i know if the above suggestions is taken care in the release dated 20 Feb 2013[projects/gss] , so that it would be easy to check whether this great piece can be explored further as per the requirement.?

dhavyd’s picture

Yes, it was... But I've just done a new release with additional bug fixes... But I don't understand what you mean by "... it would be easy to check whether this great piece can be explored further as per the requirement"?

kancharlawar’s picture

ohh...i just wanted to use this module for checking if it really fits in the requirement...thanks dhavyd for the attention...

dhavyd’s picture

Status: Active » Closed (fixed)

No problem... Then I can close this issue...

dhavyd’s picture

Issue summary: View changes

typo.