All Low add-ons are now owned by EEHarbor. Read the blog post.

Support archive

Any way to see the errors from Low Google search?

nrackleff 29 Nov 2012 19:04 question, complete

Is there any way to see the errors from Low Google search response? I'm seeing Error getting http://www.google.com/cse?... with a message to check settings. It would be helpful if I knew what the error was. Also, are there settings for the module, or does this refer to the tags. My suspicion is that the free version of google search cannot be accessed from a different URL than the site, which is what I am trying to do from the dev environment. Thanks for your help.

Replies

  1. Low 29 Nov 2012 21:22

    If I'm not mistaken the CSE is the free version of Google's custom site search, which doesn't return XML. Therefore, it's not compatible with Low GoogleSearch. You need the (paid) custom search: http://www.google.com/enterprise/sear... in order to get the results to work with Low GoogleSearch.

  2. nrackleff 29 Nov 2012 22:25

    Google appears to confirm this in their side-by-side comparison. http://support.google.com/customsearc...
    I will see if the client would like to upgrade. $100 / year is not a lot to be able to have nicer looking integrated results. Thanks for the reply.

  3. nrackleff 1 Dec 2012 20:24

    We upgraded our client to Site Search, but I am still getting an error. Is there something I need to do other than upgrading? We are attempting to do this from a dev server that is not in the same domain as the live site. Error: "You are not authorized to perform this action".

  4. nrackleff 1 Dec 2012 21:52

    Another update. I'm still getting the not authorized error in the plugin results, but if I just put the string http://www.google.com/cse?q=kidney&ou... (replacing [hidden] with the actual ID) in my browser, I do get XML returned. I am not browsing from an IP under the domain.

  5. Low 2 Dec 2012 09:47

    The "You are not authorized" error points to the Secure Forms setting in EE. You can turn that off for Low GoogleSearch by adding secure="no" to the Form tag parameters.

  6. nrackleff 3 Dec 2012 17:01

    Thanks for the response. I have added secure="no". I am still getting errors. this time it says Error getting http://www.google.com/cse?q=heart&out...
    Please check your settings or try again later. I do see XML returned when I paste the URL into the browser. Here are my form and results tags.

    {exp:low_googlesearch:form secure="no" results_page="search/results"}
    <input type="text" id="keywords" name="keywords" class="input-text" style="border: 1px solid #ccc;"/>
    <button type="submit" id="searchSubmit" name="searchSubmit" class="input-submit">Search</button>
    {/exp:low_googlesearch:form}
    </div>
    {exp:low_googlesearch:results keywords="{segment_3}" secure="no" cx="005806001714003133742:aicr01arhcy" client="google-csbe" site="silvertonhealth.org" oe="utf8" results_page="search/results"}
    ...
    {/exp:low_googlesearch:results}



    I am using EE 2.5.3

  7. Low 3 Dec 2012 17:12

    Try removing the client="" and site="" parameters, which should play better with Google's hosted version.

  8. nrackleff 3 Dec 2012 17:16

    Didn't help, still getting. Error getting http://www.google.com/cse?q=heart&out...
    Please check your settings or try again later.
    Current string {exp:low_googlesearch:results keywords="{segment_3}" secure="no" cx="[hidden]" oe="utf8" results_page="search/results"}

    Anything else I might try?

  9. Low 3 Dec 2012 17:21

    So, it's not working with this opening tag? It is on my machine... 

    {exp:low_googlesearch:results keywords="{segment_2}" cx="[your-cx-key]"}

  10. nrackleff 3 Dec 2012 17:26

    I'm using segment_3, but no, it is not working from our dev server in the template, but it does return XML if I paste the link in my browser.

  11. Low 3 Dec 2012 17:31

    Hmm... is your dev server behind a firewall, maybe? Or are you sure the server has either allow_url_fopen or Curl enabled?

  12. nrackleff 3 Dec 2012 17:31

    Just made an interesting discovery. I have a duplicate of the site on localhost. The code works fine from there, so it must be something in our dev setup. I will look into it from that end. Thank you for your help. I will let you know what I find.

  13. nrackleff 3 Dec 2012 17:35

    I don't believe it's behind a firewall. I will check on allow_url_fopen and/or Curl.

  14. nrackleff 3 Dec 2012 17:39

    allow_url_fopen is on. Checking the firewall issue.

  15. Low 3 Dec 2012 17:45

    It's definitely something environmental... Your dev server doesn't seem to be able to get the XML while both our local environments can... Keep me posted...

  16. nrackleff 3 Dec 2012 17:55

    Will do. I notice that my local server (in MAMP) does have cURL, but the dev server does not. They both have allow_url_fopen. cURL is not required if allow_url_fopen is on, right?

  17. nrackleff 3 Dec 2012 18:22

    We installed cURL and it is working now. It was not working with allow_url_fopen by itself. Is this just an anomaly with our server, or do you need both? thanks again for your help with this issue.

  18. Low 3 Dec 2012 18:55

    It does an ini-check to see of allow_url_fopen is available. If not, it checks cURL. If that isn't available, it bails out. Maybe your dev server returned FALSE in the first check... In any case, you should only need one.

    Anyway, glad it's working now!