Page 1 of 1

Google Search borked?

Posted: Tue Jul 12, 2011 11:06 am
by Professor Brian Strain
Just tried searching on the main site, got a Google Sorry page telling me I was sending an automated search?

Have they changed something or is it a problem on ZZAP!s side?

(Search done with Firefox 5)

Posted: Tue Jul 12, 2011 1:13 pm
by Iain
Em, I am getting the same message. Going to google.com directly and searching works fine, so I doubt our IPs are blocked.

The IP of the website shouldn't matter since the form is submitting from the user's IP.

Maybe my Google search code is out of date.... I'll give it another day and see if it rights itself before looking into it more.

Thanks for the info.

Posted: Tue Jul 12, 2011 6:22 pm
by andy vaisey
Getting same here in FF5 and Chrome.

How odd...

Posted: Fri Jul 15, 2011 3:05 pm
by Iain
It seems there is a new Google custom search for sites and it looks like they have just "switched off" the old version without announcing it or giving warning (according to some forum posts anyway).

So I'm in the process of trying to fit the new custom search into the site, I have a feeling I won't be able to customise its look like I did with the old one since it's mainly in a JS include file...

Posted: Fri Jul 15, 2011 11:36 pm
by Professor Brian Strain
Iain wrote:It seems there is a new Google custom search for sites and it looks like they have just "switched off" the old version without announcing it or giving warning (according to some forum posts anyway).

So I'm in the process of trying to fit the new custom search into the site, I have a feeling I won't be able to customise its look like I did with the old one since it's mainly in a JS include file...
Can you do a Google search for the code you need?

*ducks*

Posted: Sat Jul 16, 2011 11:54 am
by Iain
All fixed now. I've lost the nice Def Guide logo that used to be on the results page but I can host the results on my own page and do that at a later stage...

Pretty embarrassing looking at the source code on my front page :( 739 W3c validation errors :-o