Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Not a Bug
-
Affects Version/s: 1.3.0
-
Fix Version/s: None
-
Component/s: Site Generation Service
-
Labels:None
-
Environment:
Optus Production
Description
Site Generation Service uses Google Maps to perform a geo lookup on the merchant's address in order to find the lat/long for the merchant. This lat/long is then used on the generated website to make the map request whenever a browser opens the page.
The html that is generated by site gen looks like this:
<meta name="viewport" content="initial-scale=1.0, user-scalable=no" /><style type="text/css"> html
body
{ height: 100%; margin: 0; padding: 0 }#map_canvas
{ height: 100% }</style><script type="text/javascript" src="http://maps.googleapis.com/maps/api/js?sensor=false&client=gme-thesearchagencyinc1"></script><script type="text/javascript"> function initialize() { var latlng = new google.maps.LatLng(-33.7904955, 151.1228434); var myOptions =
{ zoom: 13, center: latlng, mapTypeId: google.maps.MapTypeId.ROADMAP }; var map = new google.maps.Map(document.getElementById("map_canvas"), myOptions); var marker = new google.maps.Marker(
{position: latlng, map: map, title:""}); }</script>
</head>
<body onload="initialize()">
<div id="map_canvas" style="width:100%; height:100%"></div>
</body>
</html>
Note that the lat/long is included and that the token used for the Google Maps call is gme-thesearchagencyinc1
The initial call to get the lat/long that site gen makes is supposed to use a different token (gme-thesearchagencyinc) however when I look at usage statistics in Google I see plenty of hits to the first token and zero hits (ever) on the second token. My suspicion is that we are erroneously using the wrong token in Site Generation for the initial lat/long.
Manasa, Jeff asked that you take a look at this sometime in the next few weeks and see what we are doing wrong and correct it.
