Categories: Troubleshooting and Bugs :

Google Custom Search Javascript error

Showing 1-8 of 9 messages
Google Custom Search Javascript error web_dev_guy 4/30/12 7:31 AM
So I've implement the Google Custom Search on my website and it is working, but I noticed in my console that that it keeps coming up with an ambiguous Javascript error:


I can't seem to figure out why this is coming up or what the significance of the link is. It would be great if anyone shed some light on this for me please?
Re: Google Custom Search Javascript error cjmuk70 7/8/12 6:36 AM
I'm getting exactly the same result... not sure why either....
Re: Google Custom Search Javascript error web_dev_guy 7/10/12 11:48 AM
Let me know if you find any resolution to this at all... I still haven't come up with a solution for it.
Re: Google Custom Search Javascript error JonMitten 8/9/12 11:49 AM
Same here. I get:

  1. GET http://www.google.com/uds/?file=ads&v=3&packages=search&async=2 jsapi:21
    1. google.(anonymous function).djsapi:21
    2. (anonymous function)jsapi:28
    3. (anonymous function)jsapi:18
    4. google.(anonymous function).M.(anonymous function).Dfdefault+en.I.js:359
    5. google.(anonymous function).gadefault+en.I.js:434
    6. (anonymous function):8081/:65
    7. R
Re: Google Custom Search Javascript error simonarame 9/10/12 1:44 PM
yes i also receive the error SCRIPT87 in IE9 on script default+en.I.js at line 211
Re: Google Custom Search Javascript error Anton Pirker 12/20/12 1:28 AM
Hi!

I get the same error. Has anyone of you figured out how to fix this?

Thanks,
Anton

Re: Google Custom Search Javascript error Wolf Loescher 12/29/14 2:04 PM
Here we are at the tail end of 2014, and I'm getting it now. Custom search has been in place on the site for over a year, and this is a new development (with no related code changes).

Was there ever any resolution to this issue?
Re: Google Custom Search Javascript error Fjan 12/30/14 12:52 AM
I'm seeing the same thing since about a month. The 404 also happens on the public URL for the Custom Search Engine so I'm certain it's not a configuration issue on my part.