Problems finding clickmap lib on localhost?
| Project: | Click HeatMap |
| Version: | 5.x-1.0 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | boombatower |
| Status: | closed |
Jump to:
This looks really interesting - thanks for the initial release!
I'm having a few problems getting this installed on my localhost dev server - I've checked out the dev version from cvs and I've got the clickheat library downloaded and configured at:
http://localhost/aardvark/clickheat
My drupal installation is at:
http://localhost/aardvark/drupal
When I go to the clickmap settings page at admin/settings/click_heatmap, it won't accept the path I enter (http://localhost/aardvark/clickheat), returning the error 'Valid ClickHeat installation not found at server url.'
Looking at the module code, this error appears to be because the _validate hook checks the response from click.php in the clickheat directory which it expects to return the string 'Parameters or config error' when called with no parameters.
If I manually go to http://localhost/aardvark/clickheat/click.php in my browser, 'Parameters or config error' is exactly what I get.
However, if I call the following code in the 'Execute PHP' block of devel.module (which is how the clickheat module checks)
<?php
$response = drupal_http_request('http://localhost/aardvark/clickheat/click.php');
print_r($response);
?>I get the following:
stdClass Object
(
[error] => 10060 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
[code] => -10060
)
Any ideas?

#1
Hmmm.... it appears that it might be a problem in drupal_http_request not resolving 'localhost' correctly, since setting the installation to 'http://127.0.0.1/aardvark/clickheat' works instead. Weird. Either I'm being dense, or this might need to be passed as a bug to the core queue.
I'm off to go play with heatmaps now!
#2
I can't reproduce the problem on my end. It works fine when I use localhost.
#3
I'm assuming this was just a server setup fault since it works on my end and you are responding to other issues.
#4
Sorry, yes - tried it on my Mac and that works fine.... what does that say about developing on Vista rather than a Mac?!
#5
I'm a SUSE Linux fan myself. =D
#6
Seems to not like that I closed it.
#7
Automatically closed -- issue fixed for two weeks with no activity.