Forum Replies Created
-
Posts
-
Lance is looking into it. Something changed recently and he is trying to see if it is WP, (there auto update security patch) Google or SLP.
We are having a difficult time trying to reproduce the issues on our sites.
Did you update after backing up? If you roll back SLP to 5.0.2 for instance is there a problem?
Is this the site url with issue? https://curbtheappeal.com/#HazardousSites
Alex,
Could you provide me the exact site url where the map loads so I can visualize what you are asking?
If all your locations are in UK you can use the append feature with experience add-on and it will show the areas only in UK but it will not go back to your center map at. Once the search has initiated on the site the google geocoding API kicks in.
Just using the Map domain as UK is not going to restrict searches to just that map domain you are correct. That is not how Google works.
You can help your customers out with experience add-on by providing the discrete search function
With Premier there is a limit by territory feature but it does not sound like that is what you are looking for. There is also a boundary influences guesses, but that will not limit the locations exclusively to the data set to recenter. Other option is to limit the results radius settings and radius behavior
Thanks for letting us know. I had a 1 hour meeting this morning with the SLP developer going over various scenarios and issues others were having and yours came up as well. So i received an impromptu lesson showing me where all the restrictions went , what the difference was etc, and the fact that SLP update a few months ago works differently t no longer routes geocoding requests direct to Google. Since a few releases ago, They are now routed to your WordPress install where WordPress communicates with Google. This allows your Google API keys to be secured and not leak out via JavaScript where anyone can “borrow” your API key and install it on their site while you pay the bill. Older versions of SLP didn’t care if your WordPress REST endpoints were mis-configured because it wasn’t using them
Glad to hear that the message you were seeing was indeed because of the IP address . And no it isn’t weird about the IP address, that was going to be today’s question to you after my meeting.
, Lance was explaining to me about the cpanel and the server proxy and the different IP address…..since I am really not that technical my eyes starting glazing over.
Ok, Also the SLP Developer said if you want to send screenshots to our contact us support email. he will be able to look for you as well. Screenshots should be of
1) SLP General Settings showing both Google API Key fields.
2) Google API Key DETAILS screen for the Browser Key (showing the key ID , restriction settings, etc.)
3) Google API Key Details screen for the Geocoder key.
If you use IP Address restrictions the IP address must be the direct IP address of the server not a proxy service address. Could that be why Google is sending you the API error?
P.S. Are you on SLP version 5.03 now?
Here are some cool CSS suggestions and you can see the fields that can be changed
https://docs.storelocatorplus.com/blog/store-pages-templates-slp_pages-work/
and how to make the phone clickable and the shortcode for the SEO Pages
https://docs.storelocatorplus.com/blog/make-a-dial-link-phone-number-clickable/
More info, attributes Creating StorePages scrol down to the info for custom templates
Not sure, ,what is your plugin environment, i.e Under SLp Info? will show versions etc.
https://docs.storelocatorplus.com/blog/store-locator-plus-info-plug-environment/
Andrew,
I am at a loss but have the developer trying to figure this out. It is a lot of different errors I am seeing reported by customers but they are all related to geocoder, so I do nto know if Google changed something on us yet again or what is going on. We had a customer who fixed his API key restrictions and it wirked and now the problem is back.
Long story short, can you send , via the contact us any WP debug logs you might have if you have tried that, and/or send a temporary log-in via Support for your staging site so our developer can look at it?
Ugh so frustrating I know.
Aha, This may be very helpful to solve some of our missing locations cases. I do not know if Google has yet again changed something or what, but the developer needs as much info as possible because we cannot replicate the issue on our end. We understand people wanting to restrict the APi key, in reality the chances of everyone having the wherewithal to even be able to find your API key is very small.
Do you have a test site or a staging or dev site that you might be able to provide our developer if he needs one ? (not in the forum bu via our secure support contact us)
Aha, This may be very helpful to solve some of our missing locations cases. I do not know if Google has yet again changed something or what, but the developer needs as much info as possible because we cannot replicate the issue on our end. We understand people wanting to restrict the APi key, in reality the chances of everyone having the wherewithal to even be able to find your API key is very small.
Do you have a test site or a staging or dev site that you might be able to provide our developer if he needs one ? (not in the forum bu via our secure support contact us)
Ok, i had to reformat your text for that one.
can you go to the SLP general Tab under Admin and enable Debug. and run the debug log . You will see the link to docs on the side: “Hover over a setting to learn what it does.
Enable WP Debug
Turns on WP_DEBUG and WP_DEBUG_LOG. Use with caution: it can display warnings and errors on your web pages. View debug.log
View the documentation for Enable WP Debug.“
I cannot see the screenshot you attached due to its size , but thats ok. The developer and I are mystified because we cannot reproduce this issue in any of our test sites or domains. a couple of people have reported similar. I sent Lance your plugin environment. So unfortunately we need you to provide us a little more help to resolve the issue or to find the conflict with your configuration or with another plugin.
Could you go to the SLP General/Admin and enable WP debug. Please send us the debug log. , send it to the contact us support
Do you see the drop down menu under Maps where to select Map domain under SLP? Some people have reported some missing on sites they already had running but updated. Trying to track down any culprits that may be json related.
See docs and the screenshot in the docs
This is not the same as geocoding APi key, it is what Google geocoding needs to find the region , i,.e map domain.
Hey Andrew, We are tryint o track down the bug,
On the site that you already have and returning errors, Do you see the map domain list? If you cannot see screenshot see where the map domain dropdown menu is under Documentation about how to select map domains
So you do not see this screenshot attached??/ Documentation https://docs.storelocatorplus.com/blog/google-map-domains-supported-in-slp/
Drew you mentioned SSl…did you recently migrate site to Https? Is there a difference between the staging site SSL and the actual live site?
Drew can you try something for us on the site url that isnt working? Goto Settings/MAP and map domain and set it to something else, save, then set it back to United States or whatever you had before
And report back what it says.
Hmmm,,, Ok So here is a test that Lance would like you to try, we noticed there was no region set on your map search when I searched it and sent the string to Lance:
try going to Settings/map/map domain and set it to something else, save, then set it back to United States
And report back if you see changes, errors or fixes
Here is an article to help you with what you need to know about Google keys. There should be two boxes under the google , MAPS AND PLACES, CHECK BOTH OFF
https://www.storelocatorplus.com/wordpress-store-locator-plus-google-api-key/
I just answered in Premier forum, also running by Lance, but I see 7 errors when I inspect your site, not all are from performing the search. There is an issue with the Geocoder APi key on your site is my guess but I am running it by Lance.
If you do not have any referrer restrictions you do not need to be obtaining a unique geocoding KEY. I can see your geocoding key when I inspect and search in that site so I am guessing that may be one of the issues.
Yes The error is the same , you can see it if you just use the browser tool to inspecyt and look under the console tab at the bottom when it opens up
Failed to set referrer policy: The value ” is not one of ‘no-referrer’, ‘no-referrer-when-downgrade’, ‘origin’, ‘origin-when-cross-origin’, ‘same-origin’, ‘strict-origin’, ‘strict-origin-when-cross-origin’, or ‘unsafe-url’. The referrer policy has been left unchange
The other error that I see now when using the “search for a specific zip code; using browser console inspector is a 404 error.
I am discussing this with the developer.
Does your Google APi have a referrer restriction? If I do not add anything into the search form and change radius and click on find locations the locations appear. But when I type in a zip code it appears the geocoder is not working. I am going over the issue with lance. The geocoder APi on your site does not seem to be working correctly. Did you update your APIs when you added a billing account with Google?
Buy Here for WooCommerce has not been updated or tested with current versions of WP or SLP. I will ask the developer if he has any ideas. I do not believe you need it but I will ask the developer.
Awesome, thx for letting us know. bSLP also updated the base plugin to 5.0.3 that took care of the accent in the search. WP updates required SLP updates to correct for missing spaces, commas or character, language accents
Awesome, thx for letting us know!