[Shad]

I’m not sure what you’re asking but Lance designed the settings and page layout for us custom. Can you ask him?

We’re not willing to stick with the older version because of the vulnerabilities.

And yes, the sites are the same now as we went ahead with the update and rolled the new version out to staging and live stacks.

[Shad]

On an interesting note, using the beta versions of plugins we are getting the following message in the Schedule tab of the General section when the “Center Map at” is set to Denver, Colorado.

“2016-12-22 21:44:42 :: schedule :: Recalculate initial distance needs map center to have a valid longitude. ( -104.990251 )”

 

The Center Longitude Fallback automatically fills out to “-104.990251” when centering the map at Denver, Colorado. But if I go to google and grab the coordinates from there it gives me “-105.1352965”. Using that longitude then fixes the distance problem. So it seems to be that for Colorado, SLP is generating the wrong the longitude.

 

Store Locator Plus:4.7.1-beta-5

Experience:4.6.5

Power:4.7.1-beta-4

Premier:4.7.1-beta-4

 

 

This Info Cached:1482443055

Network Active:No

 

WordPress Version:4.7

PHP Version:5.6.29

MySQL Version:5.6.34

 

PHP Limit:512M

WordPress General Limit:40M

WordPress Admin Limit:512M

PHP Peak RAM:43 MB

PHP Post Max Size:8M

[Shad]

Cici,

1. Location Sensor is Off.

2. Hide Distance is off.

3. Results are set to Closest…Furthest.

 

Question for you, when you switch from Denver to Charleston SC and then back to Denver the result is then setting back to 0?

I ask because if I have the “Center Map at” (in the backend) set to Littleton, Colorado and create a new location in Denver, Colorado, the Distance is set to 0.

If I then change the Center Map at from Denver to California, the Distance will update. If I then change “Center Map At” back to Denver, Colorado the Distance not change. It stays at the distance calculated from California.

I have the same problem on multiple different sites too. I wasn’t just testing on the same site so that rules out a weird site issue. Besides testing on the plugins listed earlier I also tested on the most recent beta versions, but still wound up with the same problem.

(In the attachment is a Denver location after I had switched “Center Map at” from Florida and then back to Denver, Colorado. Distance is still showing up as 1583.4 miles).

 

 

[Shad]

Hi Cici,

The “Center Map At” that I’m changing is in the Experience > Map area. When I enter in Colorado, New Mexico or Wyoming the “Center Latitude Fallback” and “Center Longitude Fallback” are updating correctly and the so is the pin on the “Map Center Fallback.” However the “Distance” on location is still not updating in our results.

I also tried clearing out the lat/long to see if that gave me different results, but it didn’t.

Just to be clear, I have the “Center Map At” at Denver, Colorado and the Lat and Long are correct in Experience and the “Map Center Fallback” is correct as well. Our results are showing that a location in Denver, Colorado is 810.1 miles away which is the same ‘Distance’ when I had previously set the “Center Map At” to California. So even though everything is updating in Experience it’s not updating the Distance information on locations, but only when I set the “Center Map At” to one of those 3 states.

[Shad]

Hi,

Another user here, it sounds like you may need to geocode all locations. If the lat/long was not included in the import you might want to try to geocode all locations.
Navigate to to the Locations tab select a single location and geocode from the bulk actions menu, if the Location appears, you can then select all locations (depending on how many, google only allows so many per day, up to 2500 I think) select bulk actions and geocode selected.

[Shad]

Ello Cici,

Sounds like plan, and in the meantime we will update to 4.6.5 in a test environment and report if the update has resolved this bug.

[Shad]

Cool, thank you Cici.

-Shad

[Shad]

Hi Cici,

I’m working with Shad on this one.

In older versions of the plugin, even when we had store pages enabled, the [slp_location web_link] would display the website label text with a link to the location URL if there was no store page created for that particular location.

The thing is when we use [slp_location web_link], it is <span style=”text-decoration: underline;”>not</span> displaying the website label text if a store page is <span style=”text-decoration: underline;”>not</span> created. If there is no store page, no text what so ever is showing up. The website label text appears only once a store page is created for a location using the [slp_location web_link] shortcode.

– Lori

[Shad]

Looks like you may need to set your Google API Key Restriction to None.
Key restriction lets you specify which web sites, IP addresses, or apps can use this key. Learn more

• None
• HTTP referrers (web sites)
• IP addresses (web servers, cron jobs, etc.)
• Android apps
• iOS apps

Hope this helps.

[Shad]

Thanks for the info, but like you said not really a viable workaround to set restrictions to none.

We can get the front end to work with Browser Key (the map) but are unable to Geocode Locations with Browser Key.

When we use the Server API Key we can Geocode Locations, however the map will not display.

So as far as a resolution, you state that that Lance knows exactly what the issue is and that Google is aware of it?   Could you or Lance please elaborate on what the issue is, so we can harass google as well 🙂

[Shad]

As far as I recall, there is no way to update existing store pages.  You should be able to bulk edit and recreate pages (this will rebuild all selected pages as “New” pages).  Hope this helps.

[Shad]

That’s pretty much the conclusion we came to as well 🙂

[Shad]

Hi Cici,

From what we can tell, it is NOT the SLP Plugin itself and is solely a Google Maps API update.  We will keep you posted if we run across any new info.

Shad

[Shad]

https://developers.google.com/maps/pricing-and-plans/standard-plan-2016-update

Looks like Google Maps API plans has updated.

“Active domains created before June 22, 2016, continue to be able to access the Google Maps JavaScript API, Static Maps API, and Street View Image API without an API key. They are not affected by keyless access being unavailable for new domains.”

[Shad]

I am not the author of plugin, just a long time user of the SLP products.  Saw the post about Pages Map not displaying and thought I would share my experience.

[Shad]

I had a similar issue and that solved it… and even now on a dev site, if I change map Height Units to a %, Pages will no longer display map.  Your environment may differ from mine, but its a quick test and possible solution.

[Shad]

Check to see if your Map Height Units is set to %.  Try changing to px and see if Pages map loads.

[Author]

Posts