fostermade

It doesn’t have much to do with the original issue other than to say I’m forced to open directions in a new window since not doing so throws an error.

I receive that error when I click on the “Directions” link in the search results, if “Open directions in a new window” is unchecked.

@tijmensmit in response to your question from earlier, yes, I removed all of the conditionals within the reverseGeocode function and kept only the callback so it looks like this:

function reverseGeocode( latLng, callback ) {
geocoder.geocode( {‘latLng’: latLng}, function( response, status ) {
callback();
});
}

That paired with opening the directions in a new window works. Would you still like a screenshot of my settings or do you have it pretty well narrowed down now?

@tijmensmit I have backed my changes out and unchecked “Open directions in a new window” and it has fixed the issue for me as well. The only problem now is that when I click on the “Directions” link I receive a JavaScript alert stating: “Something went wrong, please try again!”

@tijmensmit I removed everything except the callback(); and the entire issue has cleared up. There is definitely something else going on there when the reverseGeocode function fires during a submit of the search form.

Also, thanks for taking the time to help troubleshoot this. Much appreciated!

• This reply was modified 6 years, 5 months ago by fostermade.

@tijmensmit, in the unminified wpsl-gmap.js file on line 1148 there is a conditional check for status that is causing the error. If that conditional is removed and the callback() is allowed to fire, results are returned properly. This is within the “reverseGeocode” function.

I am having a similar issue. Some postal code searches yield no results despite having many locations in and around said postal code. The same holds true for certain city names.