Thanks for the report. I welcome others to try, and to keep trying. I
initially dismissed it as a fluke, or a transmission issue between the
site and the api... but the customer gets several calls a day about
it, and I've now seen it for myself.

@blob, the 8th location, KR Retail is there. It's just under Leavitt's
Kitchen. Those two stores are only a mile or so apart, so zoomed out
to that level, they overlap and look like one. If you zoom in on KR
Retail, you'll see them both.  Thank you for your attention to detail
and for reporting that. For a moment, I thought I had something else
to fix... thank goodness not!

Please keep trying, especially mac users. This client's whole business
revolves around this dealer locator, and they're never going to leave
me alone until it works reliably. There's no way I can troubleshoot an
erratic issue unless I can get more eyes looking at it. And if it's an
API issue, we need to get it fixed for everyone else who might be
experiencing the same thing.

Here's the snippet of script I'm using to error check the results (in
the searchLocationsNear function):

if (markerNodes.length<=0) {
                alert("We're sorry, no dealers could be found matching your
search criteria. Please double-check the address entered and/or
broaden your search radius, then try again. If you still do not find a
dealer close by, please call us at (801)383-1920, or search the
internet to find one of our authorized online retailers.");
        } else {
                map.fitBounds(bounds);
                locationSelect.style.visibility = "visible";
                locationSelect.onchange = function() {
                        var markerNum =
locationSelect.options[locationSelect.selectedIndex].value;
                        google.maps.event.trigger(markers[markerNum], 'click');
                };
    }


Previously, that section of code looked like this:

map.fitBounds(bounds);
                locationSelect.style.visibility = "visible";
                locationSelect.onchange = function() {
                        var markerNum =
locationSelect.options[locationSelect.selectedIndex].value;
                        google.maps.event.trigger(markers[markerNum], 'click');
                };

... which would simply dump you into the middle of the ocean by
australia (I'm assuming at lat=0 lng=0) if there were no results.

Is there anything wrong with this section of code that anyone can see?

thanks again,
Blaine

-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps JavaScript API v3" group.
To post to this group, send email to google-maps-js-api...@googlegroups.com.
To unsubscribe from this group, send email to 
google-maps-js-api-v3+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-maps-js-api-v3?hl=en.

Reply via email to