Thanks for replying ...

I was merely following the instructions on the web page I linked ...

https://support.google.com/code/answer/74501

... viz, the dynamic loading equivalent of Google's own static loading 
example given there, in other words the dynamic loading equivalent of this:

<script type="text/javascript" 
src="http://www.google.com/jsapi?key=YOUR-KEY";></script> 
<script type="text/javascript"> 

        google.load("search", "1");

        // ...
        google.load("maps", "3");

</script> 


It worked until first the 302 affair of a week or two back previously 
posted about, but I was able to fix that, until now the search itself is 
giving a 404 seemingly as from this last weekend.  It may have been 
deprecated in 2010, and was supposedly switched off in 2014, but I had no 
knowledge of that, and it was working last week.

And there's still the question of why Google's own documentation is still 
claiming that it's current, apparently a decade after its deprecation was 
announced?

Apparently the equivalent replacement service is the Geocoding service 
which is part of Google Maps.  I have a Google Maps app and apparently 
Geocoding is already enabled as part of it, but when, following Google's 
own example page ...

https://developers.google.com/maps/documentation/geocoding/start

... I put the followiing into a browser's address bar ...

https://maps.googleapis.com/maps/api/geocode/json?address=<MyPostcode>+UK&key= 
<https://maps.googleapis.com/maps/api/geocode/json?address=IV274DN+UK&key=>
<MyKey>

... I get back (I have to look at the page source to see it) ...

{ 
   "error_message" : "API keys with referer restrictions cannot be used 
with this API.", 
   "results" : [], 
   "status" : "REQUEST_DENIED" 
} 

... so now I'm wondering if the Geocoding API instructions are fully pukka, 
or if they are out of date as well!


On Monday, 6 July 2020 13:39:57 UTC+1, jgeerdes [AJAX APIs "Guru"] wrote:
 

> I don't know what API you've been using, but the suite of services that 
> was originally known as the AJAX Search APIs was shut down. Other services 
> which were rolled out under the AJAX APIs loader have continued to function.
>
> jg
>
> On Mon, Jul 6, 2020 at 6:57 AM JavaJive <... <javascript:>> wrote:
>
>> As per subject, two questions stand out about this:
>>
>> ? If it was turned off in 2014, how is it that my site has been using it 
>> without problems for all these years since, until this last weekend?
>>
>> ? Why has its documentation existed on Google's site over all the 
>> intervening years and stills exist now, with a current date?
>>
>> https://support.google.com/code/answer/74501
>>
>>
> -- 
> Rev. Jeremy R. Geerdes, Pastor
> Debra Heights Wesleyan Church
> 4025 Lower Beaver Rd
> Des Moines, IA 50310
>
> (515) 344-3037
> jgee...@debraheightswesleyan.org <javascript:>
> http://dhw.church
>

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Google AJAX APIs" group.
To post to this group, send email to
google-ajax-search-api@googlegroups.com
To unsubscribe from this group, send email to
google-ajax-search-api+unsubscr...@googlegroups.com
To view this message on the web, visit
https://groups.google.com/d/msgid/google-ajax-search-api/041fefe3-1d92-46c7-a009-bf08c7c0d405o%40googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-ajax-search-api?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Google AJAX APIs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-ajax-search-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-ajax-search-api/041fefe3-1d92-46c7-a009-bf08c7c0d405o%40googlegroups.com.

Reply via email to