Forum Replies Created
-
Posts
-
Ok, I just searched Google commercial maps and typed in Victoria British Columbia , it showed the correct location but look at what it returned for lat long etc
https://www.google.com/maps/place/Victoria+817205,+Romania/@48.4262871,-123.394242,13z/data=!3m1!4b1!4m13!1m7!3m6!1s0x40b0e48f03d9410f:0x3fe626b121cc0c82!2sVictoria+8
So suspicions confirmed, Googles Algorithm is screwed up even on their own site . I would write to them in their support, and ask them why they are adding +Romania before the lat and long????????
The only other thing that I did mention are the Premier features,.,,,,not adding discrete filters, that is not the search enhancements I meant to point pout but the Premier either SHOW address guess or “Google address guess” feature that is part of premier subscription which you do not have. These kind of instances are exactly why the developer created those features and added them to premier . Unfortunately, I cant suggest anyone purchase or upgrade anything at the moment because the WordPress update has broken so many things, including being able to upload csv files and css features and REST API that I almost want to tell everyone to get away from their auto updaters
As far as how you are using those drop down discrete selectros you may have gone overboard with allowing city and the province and the countryyou do not need to also have province selected. You are allowing your customers to select a city and then select a province that the city may not be in and select a country as well. See the back end screenshot to clarify. It is working correctly on my site., but then again I am not searching the city Victoria BC, which as I mentioned is 100% Google issue
I also viewed your site using browser tools I inspected console for any errors and you may want to fix these.
You have a fatal error on your site. Did you migrate your site from http to https?
FATAL ERROR: Mixed Content: The page at ‘https://stogryn.ca/find-a-spa-retailer/’ was loaded over HTTPS, but requested an insecure favicon ‘http://stogrynsales.com/wp-content/uploads/2016/04/favicon-new.png’. This request has been blocked; the content must be served over HTTPS.
Also you have a lot of warnings: util.js:124 Mixed Content: The page at ‘https://stogryn.ca/find-a-spa-retailer/’ was loaded over HTTPS, but requested an insecure image ‘http://stogrynsales.com/wp-content/plugins/store-locator-le/images/icons/bulb_white.png’. This content should also be served over HTTPS.
On another note: Not sure if it is effecting how your Discrete search menu is now working, but if you use any browser dev tool and inspect all the warnings and errors you have a bunch that are coming back as “Violations” plugins.js?ver=4.9.9:187 [Violation] Added non-passive event listener to a scroll-blocking ‘wheel’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
initSideAreaScroll @ default.min.js?ver=4.9.9:3
(anonymous) @ default.min.js?ver=4.9.9:6
plugins.js?ver=4.9.9:187 [Violation] Added non-passive event listener to a scroll-blocking ‘wheel’ event. Consider marking event handler as ‘passive’ to make the page more responsive. ”
When WordPress auto updated sites a lot of themes and functions in plugins broke. If this issue just started appearing after WordPress last update Called a security update 4.9.9 there could be a lot more issues blocking REST API.
WordPress found a bug” and decided it was a major security risk and back-patched it to ALL old releases of WordPress. So WP 4.9.X gets it (4.9.3) and WP 4.8.X gets it (4.8.8) all the way back to WP 3.7.
So any site that has “do not auto-update to major WordPress release” (from 4.9 to 5.X) are still affected.
Sadly the ‘prevent major release’ updates is the ONLY switch a site admin can toggle via a simple admin interface.
“Minor” (aka security) patches CANNOT BE DISABLED except from very specialized code built into your theme
I mentioned that as well to the developer, I believe it is overall related to the map functionality features in Experience,
Yes, we have reported the issue to the developer and to WordPress. WordPress has auto updated any sites that allowed it and as a resut they added an extra layer of security that has broken Power import function.
The short term answer right now — ROLL BACK TO WP 4.9.8 or earlier and disable auto-update. Restore your backup before WordPress did this major update and screwed many plugins and themes
You will need your skilled It person to disable that WP auto update feature. It requires some skill in editing the wp-config.php file or knowing how to build a theme. Otherwise WordPress will restore and it will be back to 4.9.9 in 12 hours or less and create the whole issue over again
Since the WordPress release our developer will need to do a major rewrite of Power add-on . I do not know the ETA for the fix atm.
P.S> Our MYSLP fully managed customers are not effected because we manage the software and did not allow the “auto update” from WP to occur. It did however break our auto load direct from WordPress SLP into MYLP which was a very cool feature for people who wanted to switch over and not deal with the Google API fiasco.
Some times Google will redirect and mislead or just change the algorithms . They will not admit it of course and there seems to be no rhyme nor reason.
Google most likely has determined that Victoria is not discrete enough.
There are some search enhancements in Premier that were created to try to narrow down the search or provide hints for your customers to know they need to add more info. Or you can add verbiage instructing them to add more then just a word, for instance add Victoria and the country since there are many places in the world called victoria.
https://docs.storelocatorplus.com/blog/location-search-enhancements/
Set results settings to cast a wider net.
See here for info on results settings.
If Google cannot find the location sometimes it is useful to add more description in the search label area instructing the site visitor to add a full address etc. Google may have determined that Alta Gracia is not enough information to locate.
There are some settings in Premier to assist the customers to get a more accurate answer. Google influenced Guesses is one.
The center map at shortcode is not working at the moment and has been reported to the developer and is patched and undergoing testing ( pre release EXP 5 and the next SLP 5.1)
Something with the lats WordPress auto update is causing a glitch with some short codes..
.
For us to assist you , Please provide the information requested in the Posting guidelines,
When I visited the site both search by state and searching by entering a zip code, both returned accurate results.
P.S. Lance is also fixing a zoom setting in Version 5.1 of EXP and Premier. Stay tuned.
Lance wrote two new articles about the Geocoding, the Google API keys…
Articles are 6th in a series about Google APIs and what is needed that have been published since May.
We hope this sheds more light on the direction you need to take.
https://www.storelocatorplus.com/protecting-your-google-api-keys/
https://www.storelocatorplus.com/wordpress-store-locator-plus-google-api-key/
Hi Tyler,
I see that the site now has Power and Premier activated and it appears location sensor is on since all locations near me showed up. Are you all set now?
P.S If you found the support useful and think you could leave us a positive 5 star review, it would be very much appreciated. We are getting slammed from a few negative customers who did not understand that google changed the API terms, (which required them to update and get a key ). We know you understand and as a valued customer, a word from you in WPSLP reviews would really help us.
Thank you for letting us know. EXP has been updated to v 5 but you might want to wait a day to update, the developer found some other bug in Experience or Premier that effected some settings and he is fixing them for 5.1. I will ask him if info bubble is another issue.
I guess I misunderstood, it isnt categories that you are looking for?
I.E not looking for Categories replace location marker
If you want results interaction that is available with Premier subscription
The results interaction set of features provides a variety of visual cues on the location map to indicate the location a user has clicked when viewing a list of locations., providing a variety of additional options beyond the standard Info Bubble that Store Locator Plus displays when a location is clicked.
It looks like you had an API key but it may have been copied over incorrectly.
Your site is showing this error message: 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
I have blanked out the keys, . I can see them using the Browser tools, inspect, under console. it showed that there were keys entered but they are not associated with the project. You need to add your credit card info on Google site to use the APi keys. You might be able to contact Google support for non profits to see if they have special rates for non profit organizations.
https://support.google.com/nonprofits/troubleshooter
P.S. The Power addon needs to be activated and that is when you will see the setting to turn on or off the Location sensor check box. i.e in docs link above
That is 100% dependent on the browser, your visitors settings on their search (i.e allow cookies etc) your ssl cert. That is not something we control. For instance Firefox always asks if the person wants to allow the site to know their location. Chrome = never asks if you have a secure site and you have location sensor checked off under the general.user interface box.
See information in documentation about Location sensor
Please refer to the documentation Map Marker, or custom map markers in the documentation.
You can identify markers by categories and then set the map markers by categories. To identify a location as belonging to a category is available with the Power add-on.
Please refer to the documentation Map Marker, or custom map markers in the documentation.
You can identify markers by categories and then set the map markers by categories. To identify a location as belonging to a category is available with the Power add-on.
I do not follow your question. What are you asking? If I find you in Order system it appears you have the Premier subscription and that you have downloaded the add-ons and premier plugin 6 times. Is this your site (based on an older post)
https://strykerradios.com/find-store-for-10-meter-radios/
If so I do not see any errors.
What versions of SLP and the add-ons are you on?
Please read the posting guidelines and provide the information requested, formulate a specific question with details and a screenshot of your SLP Plugin environment and site url. If you also have ascreenshot of any error messages, or a WP DEBUG log that would be helpful.
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.
