No store displayed

Having the same issue with a project I’m working on as well. Hopefully can be quickly patched by the author.

Something not working as expected doesn’t mean there’s a bug in the store locator.

What’s the exact shortcode your using? Your stores are set to published? The preview map in the admin editor shows the location in the expected location? Does it work fine with a default WP theme?

@vinylthieves what’s the URL?

@tijmensmit Of course, I don’t mean to just infer that that was the case.

In my specific situation, I’m using the [wpsl] shortcode on a specific page, and I’m also receiving the warning that @erwangleo described above. The map itself does not load, and I’m left with an empty .wpsl-gmap-canvas container.

If I use your wpsl_gmap_api_version filter, I can clear the RetiredVersion warning by setting that filter to ‘weekly’, and that makes the map return.

I do personally think the default version should increased to at least 3.36 to keep up with the Maps API itself, however if @erwangleo uses the filter that I’ve described above, then they should be okay.

@tijmensmit I appreciate the forethought to include that as that solved my specific problem. I apologize for inferring initially that it was strictly a bug with your plugin. I appreciate the work you’ve clearly invested into this, and I appreciate the response!

@tijmensmit Thank you for the fast answer, I’m currently using the shortcode [wpsl template=”custom”]. I tried with [wpsl template=”default”] on a test page, same result. I also tried on the Twenty Nineteen theme, still nothing. The preview map is displayed on the plugin settings page and all the stores are published, it’s a real mystery to me.

Don’t know if there’s an link, but I’m currently working on a pre-production site on a multi-domain hosting. The other sites are not using Google maps, but can this one be impacted by this setup ?

@vinylthieves I tried the wpsl_gmap_api_version filter, set to “weekly”, written in the functions.php file. I have the same warning. Weird.

Hi
fixed it by changing version to 3.36 in function file ,
Google info “If you do not explicitly specify a channel or version, you will receive the weekly channel by default. If you’re on the premium plan and do not explicitly specify a channel or version, you will receive the quarterly channel by default. If you specify an invalid version, you will receive your default channel.
Choosing the weekly channel

For most applications, we recommend the weekly channel. This is the most current and up-to-date version and contains the latest bug fixes and performance improvements. You can specify the weekly channel by loading the Maps JavaScript API with the following script tag:

<script async defer
src=”https://maps.googleapis.com/maps/api/js?v=weekly
&key=YOUR_API_KEY&callback=initMap”>
</script>

Currently, the weekly channel is version 3.36. This version is updated weekly with new features, bug fixes, and performance improvements.

In mid-May, the weekly channel will be updated to version 3.37. At that time, the new version may remove deprecated features, and/or introduce backwards-incompatibilities.
” .

Good to hear that changing the Google Maps version fixed it, to be sure that others won’t also run into this issue I will update it today.

The reason I set a fixed version in the past was to prevent things from breaking in the first place when a new Google Maps version was released.

But I do suspect it’s a combination of things with current active plugins / used theme. I can’t replicate this issue with a few themes that I tried when I use the current Google maps version that’s loaded with 2.2.20.

@edrism Thanks a lot ! I’ve changed the version as you said and it works well now !

@erwangleo, Glad to hear that, thanks

The latest update by default now loads 3.36 as well.