search

Lamhot / php-google-map-api

Automatically exported from code.google.com/p/php-google-map-api
0 stars 0 forks source link

Tale of the non-existant Polyline. #33

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Polyline not rendering correctly on Firefox 4.

//Build address array for polyline
while ($row = mysql_fetch_array($result, MYSQL_ASSOC))
{
    $polyline_array[] = array('long' => $row['longdec'], 'lat' => $row['latdec']);
}

// make the polyline
$polyline_id = $MAP_OBJECT->addPolylineByCoordsArray($polyline_array, 
$id=false, $color='red', $weight=2, $opacity=.8);

?>
<html>
<head>
<?=$MAP_OBJECT->getHeaderJS();?>
<?=$MAP_OBJECT->getMapJS();?>
</head>
<body>
<?=$MAP_OBJECT->printOnLoad();?>
<?=$MAP_OBJECT->printMap();?>
</body>
</html>

This code has worked fine for me for a long time, with values coming from a 
database with valid data. In the generated source (too large to paste), 
everything is pristine. All javascript is there, no javascript errors, all 
points to plot out are in the source correctly. Instead, nothing is shown.

I'm using Firefox 4, renders fine on IE9 (literally, the opposite of what I 
want/need, trying to steer far away from internet explorer.).

Original issue reported on code.google.com by arf...@gmail.com on 16 Apr 2011 at 6:50

GoogleCodeExporter commented 9 years ago 
Sorry, also, using 3.0.

I also tried updating to the latest SVN of your 3.0 lib, and still nothing.

It's 5am, I knew I'd forget some details. :)

Original comment by arf...@gmail.com on 16 Apr 2011 at 6:58

GoogleCodeExporter commented 9 years ago 
Sorry, also forgot to mention that it doesn't work in chrome either.

Original comment by arf...@gmail.com on 16 Apr 2011 at 7:06

GoogleCodeExporter commented 9 years ago 
Sorry about this report. It appears google changed something in their API, 
because magically everything is working again for multiple sites, without 
anything being changed.

Please close this issue.

Original comment by arf...@gmail.com on 4 May 2011 at 4:38

GoogleCodeExporter commented 9 years ago 
There was an issue similar to this that was addressed in the group - I believe 
it's related to using a "css compliant color value" (in your case the word 
"red"), instead of the full hexidecimal value.  Not sure if that's related, but 
seems like it could be, and AFAIK, this has been fixed on Google's side of 
things and/or the browsers themselves.

Original comment by b...@mycnl.com on 25 Sep 2011 at 5:52