Forum Replies Created
-
Posts
-
Please read posting guidelines and provide your version information.
That site has the wrong geocoding API and returning these errors
Geocoding Service: This API project is not authorized to use this API. For more information on authentication and Google Maps JavaScript API services please see: https://developers.google.com/maps/documentation/javascript/get-api-key
The initial distance setting is used by Store Locator Plus to boost performance when loading the initial map. It uses SQL index on a numeric value to select a subset of data versus calculating values for potentially thousands of locations and then filtering based on the calculation.
Your site is showing Tulsa Ok , so assume you have your center map at setting as United States. Google determines the Midwest as center of US.
Current version SLP 5.0 has improved the communications with Google and has eliminated many of the over and over general “rety” geocoding settings so that Google does not time out.
Looking at your site it looks like you are using version 4.7. Sorry any patches that have been made regarding distance etc occurred much later versions as WordPress security patches were updated. We do not support that version of SLP. Once any security issues are known we MUST update our software in accordance with WP terms and best practices.
You can scroll through the many pages under NEWS for information included with each release and also notices about Google API changes.
Consider signing up for news or peruse through the many pages in News regarding these releases
And over a year ago important patches and updates were announced
Another News example regarding the WP update to 4.8.2 requiring SLP update.
I just went to your site. I typed in 29464 and find and all the locations near that zip code came back no problem. So if Google is returning a “cannot find this location try another, then Google algorithms is not finding the location. Not sure what your question is.
Did you leave debug on your live production site???? You should never debug on your live productions site. This error is coming back when I use dev tools inspect console
rrorUtils caught an error: “<![EX[[“Tried to listen to element of type %s from %s: %s”,”click”,”Error”,”C…”. Subsequent errors won’t be logged; see https://fburl.com/debugjs.
reportError @ 3Mv-pEygVoC.js:55
k.$FBLogMessage1 @ 3Mv-pEygVoC.js:96
k.mustfix @ 3Mv-pEygVoC.js:96
listen @ 3Mv-pEygVoC.js:261
k @ Qi010IqKWlT.js:14
initializeClickLoggers @ Qi010IqKWlT.js:14
(anonymous) @ 3Mv-pEygVoC.js:124
applyWithGuard @ 3Mv-pEygVoC.js:55
d @ 3Mv-pEygVoC.js:55
A @ 3Mv-pEygVoC.js:38
y @ 3Mv-pEygVoC.js:38
H @ 3Mv-pEygVoC.js:38
a.$12 @ 3Mv-pEygVoC.js:124
applyWithGuard @ 3Mv-pEygVoC.js:55
a.$11 @ 3Mv-pEygVoC.js:124
(anonymous) @ 3Mv-pEygVoC.js:124
k @ 3Mv-pEygVoC.js:124
a.$5 @ 3Mv-pEygVoC.js:124
a.handle @ 3Mv-pEygVoC.js:124
AsyncRequest._handleJSResponse @ neLSFZGtkcu.js:35
AsyncRequest._dispatchResponse @ neLSFZGtkcu.js:35
applyWithGuard @ 3Mv-pEygVoC.js:55
d @ 3Mv-pEygVoC.js:55
(anonymous) @ neLSFZGtkcu.js:17
e @ 3Mv-pEygVoC.js:184
applyWithGuard @ 3Mv-pEygVoC.js:55
n @ 3Mv-pEygVoC.js:103
setTimeout (async)
c [from setTimeoutAcrossTransitions] @ 3Mv-pEygVoC.js:151
a [from setTimeout] @ 3Mv-pEygVoC.js:184
(anonymous) @ neLSFZGtkcu.js:35
applyWithGuard @ 3Mv-pEygVoC.js:55
a.$6 @ 3Mv-pEygVoC.js:56
a.satisfyPersistentDependency @ 3Mv-pEygVoC.js:56
(anonymous) @ 3Mv-pEygVoC.js:152
done @ 3Mv-pEygVoC.js:152
f @ 3Mv-pEygVoC.js:152
(anonymous) @ 3Mv-pEygVoC.js:152
I.guard.propagationType @ 3Mv-pEygVoC.js:103
applyWithGuard @ 3Mv-pEygVoC.js:55
n @ 3Mv-pEygVoC.js:103
load (async)
ga @ 3Mv-pEygVoC.js:152
X @ 3Mv-pEygVoC.js:152
(anonymous) @ 3Mv-pEygVoC.js:152
Y @ 3Mv-pEygVoC.js:152
loadResources @ 3Mv-pEygVoC.js:152
AsyncRequest.invokeResponseHandler @ neLSFZGtkcu.js:35
AsyncRequest._handleXHRResponse @ neLSFZGtkcu.js:35
(anonymous) @ neLSFZGtkcu.js:35
I.guard.propagationType @ 3Mv-pEygVoC.js:103
applyWithGuard @ 3Mv-pEygVoC.js:55
n @ 3Mv-pEygVoC.js:103
f.last @ 3Mv-pEygVoC.js:100
(anonymous) @ neLSFZGtkcu.js:35
XMLHttpRequest.send (async)
(anonymous)
AsyncRequest.send @ neLSFZGtkcu.js:35
a.$1 @ x9bzV4APstX.js:11
a.componentDidMount @ x9bzV4APstX.js:11
$h @ qerPO65EAYm.js:5
Zh @ qerPO65EAYm.js:5
Xh @ qerPO65EAYm.js:5
Sh @ qerPO65EAYm.js:5
wh @ qerPO65EAYm.js:5
ei @ qerPO65EAYm.js:5
fi @ qerPO65EAYm.js:5
li.render @ qerPO65EAYm.js:5
(anonymous) @ qerPO65EAYm.js:5
ci @ qerPO65EAYm.js:5
oi @ qerPO65EAYm.js:5
render @ qerPO65EAYm.js:5
i @ qerPO65EAYm.js:4
j @ qerPO65EAYm.js:4
(anonymous) @ 3Mv-pEygVoC.js:124
applyWithGuard @ 3Mv-pEygVoC.js:55
d @ 3Mv-pEygVoC.js:55
A @ 3Mv-pEygVoC.js:38
y @ 3Mv-pEygVoC.js:38
H @ 3Mv-pEygVoC.js:38
a.$12 @ 3Mv-pEygVoC.js:124
applyWithGuard @ 3Mv-pEygVoC.js:55
a.$11 @ 3Mv-pEygVoC.js:124
(anonymous) @ 3Mv-pEygVoC.js:124
k @ 3Mv-pEygVoC.js:124
a.$5 @ 3Mv-pEygVoC.js:124
a.handle @ 3Mv-pEygVoC.js:124
handleServerJS @ 3Mv-pEygVoC.js:245
applyWithGuard @ 3Mv-pEygVoC.js:55
n @ 3Mv-pEygVoC.js:103
3Mv-pEygVoC.js:55 ErrorUtils caught an error: “<![EX[[“Tried to listen to element of type %s from %s: %s”,”click”,”Error”,”C…”. Subsequent errors won’t be logged; see https://fburl.com/debugjs.
reportError @ 3Mv-pEygVoC.js:55
k.$FBLogMessage1 @ 3Mv-pEygVoC.js:96
k.mustfix @ 3Mv-pEygVoC.js:96
listen @ 3Mv-pEygVoC.js:261
k @ Qi010IqKWlT.js:14
initializeClickLoggers @ Qi010IqKWlT.js:14
(anonymous) @ 3Mv-pEygVoC.js:124
applyWithGuard @ 3Mv-pEygVoC.js:55
d @ 3Mv-pEygVoC.js:55
A @ 3Mv-pEygVoC.js:38
y @ 3Mv-pEygVoC.js:38
H @ 3Mv-pEygVoC.js:38
a.$12 @ 3Mv-pEygVoC.js:124
applyWithGuard @ 3Mv-pEygVoC.js:55
a.$11 @ 3Mv-pEygVoC.js:124
(anonymous) @ 3Mv-pEygVoC.js:124
k @ 3Mv-pEygVoC.js:124
a.$5 @ 3Mv-pEygVoC.js:124
a.handle @ 3Mv-pEygVoC.js:124
AsyncRequest._handleJSResponse @ neLSFZGtkcu.js:35
AsyncRequest._dispatchResponse @ neLSFZGtkcu.js:35
applyWithGuard @ 3Mv-pEygVoC.js:55
d @ 3Mv-pEygVoC.js:55
(anonymous) @ neLSFZGtkcu.js:17
e @ 3Mv-pEygVoC.js:184
applyWithGuard @ 3Mv-pEygVoC.js:55
n @ 3Mv-pEygVoC.js:103
setTimeout (async)
c [from setTimeoutAcrossTransitions] @ 3Mv-pEygVoC.js:151
a [from setTimeout] @ 3Mv-pEygVoC.js:184
(anonymous) @ neLSFZGtkcu.js:35
applyWithGuard @ 3Mv-pEygVoC.js:55
a.$6 @ 3Mv-pEygVoC.js:56
a.satisfyPersistentDependency @ 3Mv-pEygVoC.js:56
(anonymous) @ 3Mv-pEygVoC.js:152
done @ 3Mv-pEygVoC.js:152
f @ 3Mv-pEygVoC.js:152
(anonymous) @ 3Mv-pEygVoC.js:152
I.guard.propagationType @ 3Mv-pEygVoC.js:103
applyWithGuard @ 3Mv-pEygVoC.js:55
n @ 3Mv-pEygVoC.js:103
load (async)
ga @ 3Mv-pEygVoC.js:152
X @ 3Mv-pEygVoC.js:152
(anonymous) @ 3Mv-pEygVoC.js:152
Y @ 3Mv-pEygVoC.js:152
loadResources @ 3Mv-pEygVoC.js:152
AsyncRequest.invokeResponseHandler @ neLSFZGtkcu.js:35
AsyncRequest._handleXHRResponse @ neLSFZGtkcu.js:35
(anonymous) @ neLSFZGtkcu.js:35
I.guard.propagationType @ 3Mv-pEygVoC.js:103
applyWithGuard @ 3Mv-pEygVoC.js:55
n @ 3Mv-pEygVoC.js:103
f.last @ 3Mv-pEygVoC.js:100
(anonymous) @ neLSFZGtkcu.js:35
XMLHttpRequest.send (async)
(anonymous) @ VM327:1
AsyncRequest.send @ neLSFZGtkcu.js:35
a.$1 @ x9bzV4APstX.js:11
a.componentDidMount @ x9bzV4APstX.js:11
$h @ qerPO65EAYm.js:5
Zh @ qerPO65EAYm.js:5
Xh @ qerPO65EAYm.js:5
Sh @ qerPO65EAYm.js:5
wh @ qerPO65EAYm.js:5
ei @ qerPO65EAYm.js:5
fi @ qerPO65EAYm.js:5
li.render @ qerPO65EAYm.js:5
(anonymous) @ qerPO65EAYm.js:5
ci @ qerPO65EAYm.js:5
oi @ qerPO65EAYm.js:5
render @ qerPO65EAYm.js:5
i @ qerPO65EAYm.js:4
j @ qerPO65EAYm.js:4
(anonymous) @ 3Mv-pEygVoC.js:124
applyWithGuard @ 3Mv-pEygVoC.js:55
d @ 3Mv-pEygVoC.js:55
A @ 3Mv-pEygVoC.js:38
y @ 3Mv-pEygVoC.js:38
H @ 3Mv-pEygVoC.js:38
a.$12 @ 3Mv-pEygVoC.js:124
applyWithGuard @ 3Mv-pEygVoC.js:55
a.$11 @ 3Mv-pEygVoC.js:124
(anonymous) @ 3Mv-pEygVoC.js:124
k @ 3Mv-pEygVoC.js:124
a.$5 @ 3Mv-pEygVoC.js:124
a.handle @ 3Mv-pEygVoC.js:124
handleServerJS @ 3Mv-pEygVoC.js:245
require.guard.root @ page.php?adapt_container_width=true&app_id=&channel=https%3A%2F%2Fstaticxx.facebook.com%2Fconnect%2Fxd_arbiter%2Fr%2F7LloFuHvA7I.js%3Fversion%3D43%23cb%3Df17f35d90862bd4%26domain%3Dtwooldgoats.com%26origin%3Dhttps%3A%2F%2Ftwooldgoats.com%2Ff11eebccefcb988%26relation%3Dparent.parent&container_width=0&height=545&hide_cover=true&href=https%3A%2F%2Fwww.facebook.com%2Ftwooldgoatsofficial%2F&locale=en_US&sdk=joey&show_facepile=false&small_header=false&tabs=timeline%2Cevents&width=370:20
applyWithGuard @ 3Mv-pEygVoC.js:55
n @ 3Mv-pEygVoC.js:103
(anonymous) @ page.php?adapt_container_width=true&app_id=&channel=https%3A%2F%2Fstaticxx.facebook.com%2Fconnect%2Fxd_arbiter%2Fr%2F7LloFuHvA7I.js%3Fversion%3D43%23cb%3Df17f35d90862bd4%26domain%3Dtwooldgoats.com%26origin%3Dhttps%3A%2F%2Ftwooldgoats.com%2Ff11eebccefcb988%26relation%3Dparent.parent&container_width=0&height=545&hide_cover=true&href=https%3A%2F%2Fwww.facebook.com%2Ftwooldgoatsofficial%2F&locale=en_US&sdk=joey&show_facepile=false&small_header=false&tabs=timeline%2Cevents&width=370:20
I see this warning but I do not see any Google API key errors:
DevTools failed to parse SourceMap: https://twooldgoats.com/wp-content/plugins/store-locator-le/css/csl-slplus-cleansimplewhite.css.map
I guess I misunderstood what you were referring to. I thought you were asking to have the trademark symbol removed from the name of the plugin, not having the plugin navigation button shortcut removed
Is it causing an issue in your WP admin panel or how something is functioning ? I do not know how long it has been like that. If I think of it, I will ask the developer next time we have a meeting.
The name “Store Locator Plus” is a registered trademark. as the brand is expanded to not only WP plugin and it will automatically appear that way in newer versions.
Hmm, strange, I will check with Lance and see if this is resolved in the soon to be released/published SLP version 5. I recall there being a similar issue with one site using the MYSLP SaaS software but that was using a SLP 5.0 beta 2 version which hasn’t been released to general public as yet.
I just tested SLP 4.22 with using the search button (Find Locations) and it is responding correctly. I also tried by entering text in search box and enter afterward and it also responded I am using standard WP themes but I also have Experience and Premier installed. Sudden search box issues often indicate a problem with javascript caused by themes or another plugin.
Those errors I mentioned were when I visited the site and used the browser developer tools, inspect/console.
Any additional info you can provide would be great. i.e Have you tried running the WP debugger? if so could you provide the debug log. (Make sure you clear any previous messages from earlier debug reports, we often have people send us debug logs that are outdated or have included old messages from previous test.)
Do you have a special plugin style you are using so I can test that as well to see if anything is broken there?
I note above you are not showing EXP add-on so assume you may not have any CSS added?
I did see it in the support email. It has been assigned to Lance.
On your site page “Vind Therapist’ you have two fatal errors that could effect your CSS and search form if it is interfering with SLP Javascript..
. Access to font at ‘https://hypnotherapie.nl/wp-content/themes/Avada/includes/lib/assets/fonts/icomoon/icomoon.woff’ from origin ‘https://www.hypnotherapie.nl’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.
(index):1 Access to font at ‘https://hypnotherapie.nl/wp-content/themes/Avada/includes/lib/assets/fonts/icomoon/icomoon.ttf’ from origin ‘https://www.hypnotherapie.nl’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.
as mentioned in his news feed,
https://www.storelocatorplus.com/manually-updating-wordpress-plugins/
WP or your third party update software may deploy the updates randomly. Whereas SLP requires the base plugin to be updated first .
We need information about your site and configuration.
We need information about your site and configuration.
You are using an old version of SLP, read the patches and release notes under the WPSLP changelog in WordPress to see if anything may effect you that has already been patched. I cannot support your version
We are currently on SLP version 4.9.22 with SLP 5. in testing.
You may want to review documentation for settings that can help you .
Before posting questions : Please refer to the posting guidelines.
I do not know what you have for settings currently. See suggestions in documentation
The reason for all the questions: Your initial post said there was an error about Google query limits. That has only been reported by one other customer who it turns out had multiple Premium plan APIS (pay as you go) as part of the old system. and there are different rules about those migrations and it does not appear to be a simple “take out a new project”
Google has support instructions specific to those plans.
https://developers.google.com/maps/premium/new-plan-migration
And the magic date was Nov 1 2018… Google states Starting November 1, 2018, Premium Plan customers will be able to migrate to the new Google Maps Platform pricing plan once their current Premium Plan contract expires. Only contracts whose end date is November 1, 2018, or later, are eligible to be migrated to Google Maps Platform. Contracts expiring prior to that date must be renewed on Premium Plan.
The reason I said without more info is because I do not know how many projects you have , if you were a premium Plan customer of Googles before and you blacked out the site url
Thanks for letting us know it works on other plugins, I have reported it to the developer.You have provided us as much info as you could. I am sorry I was not able to help you.
You might want to try out the MYSLP plans if you are having issues with the key and billing and various Google APIs on your new site.
Depending on how many locations and what additional features you are using the plans start as low as $5 a month
You are referring to geolocation in last post. First post you mention geocoding..
Do you have a restricted Google MAPS Javascript API key or unrestricted? Are you copying the browser MAps API key in the field called browser or in the geocoding field.
Perhaps you copied the keys in the opposite fields?
There are no problems with it working on my site… also no problems with our MYSLP customers, I cannot venture to guess what your specific issue is. without more info cannot assist you with your setup.
Sorry bout that
We cannot provide details assistance without a site url. We had a customer write in about a similar issue and found that he was using an old Google API key that they had added multiple projects to. if your “project” on your dev site is not added to whatever the API key you could run into issues
You need to review the google docs and work with them on it if you have set up the Google keys correctly (see our docs with keyword Google API) You can set query limits in the new plans but they do not work the same as the old plans that may have had limits
The developer and SLP team have written many news articles about this and other suggestions.
Hi Boone,
Sorry about that. I did get to speak to Lance. his client does not use the auto import at a specific time, so I was mistaken. they have unique directories and have support staff who update the directories and import on an as needed basis. I mentioned to him today that the WP CRON/ Remote file was not working ( he thought he fixed it a few versions ago and has not had an opportunity to test it on other sites) . Since his is fully engaged with the MYSLP Saas and two other large clients, the patch that needs to be tested and updates to the WP add-ons are behind .
Your csv file url is still publicly active right? If you want to send us a link via Conact us form I can assign it to him.
Are you manually updating or when you deactiavte the base plugin do you see an update available since SLP does not auto update like WP does. I just tested on my site , had enable Pages on before updating Power to latest version. As long as I deactivated and updated SLP base plugin first (which when I deactivated it it also deactivated my add-ons. (That is a feature that was added so people would not l crash if there was an incompatibility issue.)
I then just clicked on the update now under the Power plugin. I went back to check under General/settings
I did not lose the enable pages setting when I updated Power to 4.9.21
Did you happen to read Lances blog about not losing settings and the orde of updates?
https://www.storelocatorplus.com/manually-updating-wordpress-plugins/
I am trying to figure out the steps you are taking so I can pass the info on to Lance before the next release.
Wondering if this is your customer/ I answered this type of question a few times in forums in the past but that zip code and town seemed familiar to me. Here is the answer i provided them
https://wp.storelocatorplus.com/forums/topic/search-cannot-find-zip-code-of-one-of-the-locations/
When I visited that site I could not tell what query was being sent out since the site is highly customized.
when I went to my Commercial Google MAP and etered just the zip code i got this reply
Maps can’t find 31069
Make sure your search is spelled correctly. Try adding a city, state, or zip code.
Search the web instead
Should this place be on Google Maps?
Add a missing place
Google Maps did (in the back ground) offer suggestions, Perry GA was one suggestion but they also suggested street addresses in FL .
may be an alternative since you have search enhancements as part of premier to turn on the Google guesses function or autocomplte
Hello Robert,
The developer has a pre release version SLP 4.9.22 that I am testing, it appears to fix the directions link.
It should be published for download in a a day .
I have reported the directions redirect issue to the developer .
The renewal is not paying for premier support but for the features and functionality that are included and updated on a regular basis. For example, your site uses Category selector vertical check boxes. That is a premier function. As is many of the specialized styles, auto complete google guesses, cluster map markers, url controls etc etc.
We answered you in an email.
You need to contact Google support about the Maps API.
We do not control the query quotas or referrer restrictions. It appears you have not obtained the correct Google MAP APis r are using the referrer restriction incorrectly
if you add an IP referrer you MUST have a google geocoding API as well.
https://docs.storelocatorplus.com/blog/google-server-key/
https://docs.storelocatorplus.com/blog/google-geocoding-browser-keys/
js?libraries=geometry&language=en®ion=UK&key=AIzaSyBsLTvNNUwMnD5LYX7mEfe1oW_tmXEoXZw&ver=4.9.21:66 Google Maps JavaScript API error: RefererNotAllowedMapError
Your site URL to be authorized: https://kaymed.co.uk/find-stockist/
_.Gc @ js?libraries=geometry&language=en®ion=UK&key=AIzaSyBsLTvNNUwMnD5LYX7mEfe1oW_tmXEoXZw&ver=4.9.21:66
px.owneriq.net/stas/s/sholic.js:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
i.simpli.fi/dpx.js?cid=66111&m=0&sifi_tuid=37828&referrer=https%3A%2F%2Fkaymed.co.uk%2Ffind-stockist%2F:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
cdn.tynt.com/afsh.js:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
we do not control the zip codes, Googles algorithms does. For more accurate results Google suggests more info typed in. But as far as them misdirecting a zip code. They have done that before and we have no control over that. Perhaps you could add instructions for the search box to direct them to add more info.
As Premier there are some search enhancements that may help you
Do you have Google guesses turned on? . or autocomplete for zip codes.
https://docs.storelocatorplus.com/blog/location-search-enhancements/
Use a browser inspect tool and you will see this error message:
Failed to load resource: the server responded with a status of 404 ()
You have included the Google Maps JavaScript API multiple times on this page. This may cause unexpected errors.
Some people found that if they didn’t update WPSLP base plugin first before Updating the experience add-on they had issues as described.
Did you back-up your site before making changes? You might want to do that, then deactivate, uninstall and reinstall EXP add-on.
Another thing to check:
Check your results layout to see if the Directions follows the html anchor format.
https://docs.storelocatorplus.com/blog/results-layout-shortcodes-and-attributes/
If you are still not seeing the correct controls in your settings, you might want to restore to a previous back up if you recently updated and/or if you performed a manual update. (see authors notes about manual updates) , as always do any changes only on a dev or staging site. Double check your settings,
/*# sourceMappingURL=userinterface.css.map */