|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 28/12/2017 08:03, Thomas de Groot wrote:
> On 27-12-2017 16:10, William F Pokorny wrote:
>> On 12/24/2017 09:48 AM, Kenneth wrote:
>>> It's still not working. :-( :-(
>>>
>>> I suspect that the problem-- of interfacing with Google's
>>> changed(?)custom-search API-- is not an easy one to fix.
>>>
>>> Any new info to report?
>>>
>>>
>>>
>> I'm not aware of anything myself.
>
> It is still not working for me either. The Search field says: "Loading",
> and that is the end of the story. I have been wondering if the feature
> might not be blocked by the virus scanner/internet security facility, or
> one of the anti-spam apps I am using on Firefox, I am using...
>
>>
I get
Unauthorized access to internal API. Please refer to
https://support.google.com/customsearch/answer/4542055
Going to the said site:
This error is an indication of trying to directly access the Custom
Search Engine’s internal API (‘v1element’). Please use the code snippet
found in your CSE control panel. Learn more about Custom Search Element
V2 setup.
For programmatic access use the public CSE JSON API.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Stephen <mca### [at] aolcom> wrote:
>
> Going to the said site:
>
> This error is an indication of trying to directly access the Custom
> Search Engine’s internal API (‘v1element’). Please use the code snippet
> found in your CSE control panel. Learn more about Custom Search Element
> V2 setup.
> For programmatic access use the public CSE JSON API.
>
*Sounds* like a relatively simple fix, but I wonder.
There's a deafening silence from the POV-Ray developers so far ;-) Maybe Google
wants to charge money now for what used to be a free(?) service (?)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 29/12/2017 19:15, Kenneth wrote:
> Stephen <mca### [at] aolcom> wrote:
>
>>
>> Going to the said site:
>>
>> This error is an indication of trying to directly access the Custom
>> Search Engine’s internal API (‘v1element’). Please use the code
snippet
>> found in your CSE control panel. Learn more about Custom Search Element
>> V2 setup.
>> For programmatic access use the public CSE JSON API.
>>
>
> *Sounds* like a relatively simple fix, but I wonder.
>
It's beyond my ken. :-)
> There's a deafening silence from the POV-Ray developers so far ;-) Maybe Google
> wants to charge money now for what used to be a free(?) service (?)
>
>
>
It doesn't seem as if anyone has taken over responsibility for the
website since Uncle Ken left.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 29.12.2017 um 20:54 schrieb Stephen:
>> There's a deafening silence from the POV-Ray developers so far ;-)
>> Maybe Google
>> wants to charge money now for what used to be a free(?) service (?)
>>
>>
>>
> It doesn't seem as if anyone has taken over responsibility for the
> website since Uncle Ken left.
To the best of my knowledge, Chris Cason would be the one to turn to for
fixing such things. He's not being showered with round tuits though.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 13/12/2017 14:06, Kenneth wrote:
> Just noticed something abnormal when attempting to do a 'search' for a topic in
> the newsgroups (I'm on Windows 7 with the latest update to Firefox).
>
> The search results are limited to a few advertisements (nothing POV-ray-related
> at all), along with this warning:
>
> "Unauthorized access to internal API. Please refer to
> https://support.google.com/customsearch/answer/4542055"
Fixed now, sorry for the delay.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 31-12-2017 9:10, Chris Cason wrote:
> On 13/12/2017 14:06, Kenneth wrote:
>> Just noticed something abnormal when attempting to do a 'search' for a topic in
>> the newsgroups (I'm on Windows 7 with the latest update to Firefox).
>>
>> The search results are limited to a few advertisements (nothing POV-ray-related
>> at all), along with this warning:
>>
>> "Unauthorized access to internal API. Please refer to
>> https://support.google.com/customsearch/answer/4542055"
>
> Fixed now, sorry for the delay.
>
> -- Chris
>
Thanks indeed Chris. However, it does not seem to have solved my
problem. The attached screen dump shows the problem. The word "Loading"
blocks all further action. Any idea what causes this? Thanks!
--
Thomas
Post a reply to this message
Attachments:
Download 'search.jpg' (54 KB)
Preview of image 'search.jpg'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 31/12/2017 19:22, Thomas de Groot wrote:
> Thanks indeed Chris. However, it does not seem to have solved my
> problem. The attached screen dump shows the problem. The word "Loading"
> blocks all further action. Any idea what causes this? Thanks!
Can you try a shift-reload to clear your cache?
The 'loading' message is a static part of the page and is replaced
automatically once the google search script is successfully loaded and
functional. If that's not happening then something is preventing that
loading.
If that doesn't help please let me know.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 31-12-2017 9:27, Chris Cason wrote:
> On 31/12/2017 19:22, Thomas de Groot wrote:
>> Thanks indeed Chris. However, it does not seem to have solved my
>> problem. The attached screen dump shows the problem. The word "Loading"
>> blocks all further action. Any idea what causes this? Thanks!
>
> Can you try a shift-reload to clear your cache?
>
> The 'loading' message is a static part of the page and is replaced
> automatically once the google search script is successfully loaded and
> functional. If that's not happening then something is preventing that
> loading.
>
> If that doesn't help please let me know.
>
Oh! That is fast!
I am afraid, that did not help unfortunately.
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 31/12/2017 19:32, Thomas de Groot wrote:
> I am afraid, that did not help unfortunately.
Do you have any extensions that could be interfering with loading of
scripts from cse.google.com?
If not, can you open your browser's debugging console (usually F12),
select the 'network' tab, then reload the page? Check the network tab
for any failed requests, and the console tab for any error messages.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 12/31/2017 03:38 AM, Chris Cason wrote:
> On 31/12/2017 19:32, Thomas de Groot wrote:
>> I am afraid, that did not help unfortunately.
http://www.povray.org/search/
works for me. I searched color_map and got good results (and an amazon ad)
--
dik
Rendered 344576 of 345600 pixels (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |