Forum Replies Created
-
Posts
-
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!
More info on setting up the browser key without restrictions
See info on what not to do
If you did not set any referrer restrictions then is it possible you are using an outdated version of the Maps Javascrit API on the live site ?
https://developers.google.com/maps/documentation/javascript/v2tov3
According to Google transition team and support, you would most likely need a new key to go from version 2 to version 3. Be sure to read the article and contact Google support with questions on what you need to do, always make sure you have a backup of your site..
I just went to this site: Is this the correct url ?
https://barreamped.com/take-a-class/
It looks like you may have an old version of geocoder and/or have not correctly set up the key. The error message on that page indicates you may not be using the referrer correctly ( To use the Maps JavaScript API client side services, you will need to create a separate API key which can be secured with an HTTP referrers restriction)
The error on that public site:
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 unchanged. index
Here is an article and instructions written by the developer and in docs site. Unfortunately Google instructions stink and a lot of people are misled by Google on how to use the referrer info.
P.S. Also set the domain name to the country.
https://docs.storelocatorplus.com/blog/google-map-domains-supported-in-slp/
note that only aids Google it does not restrict the search
If you have the Experience add-on you can also use the append shortcode which will add (in the background) the Country region (CR) so results and search will be for the country designated. Experience will also allow you to have a discrete search.
Using the browser inspect tools, there is an error that is topping the load here.
https://stats.g.doubleclick.net/dc.js
I do not know if that is your issue but anything that breaks Javascript execution can break the SLP search. when I watch the performance load (using Chrome browser tools , the map is loading, The map is going to the correct area and it is going to whatever I type into the search box. I cannot replicate your issue on my test site.
See the Troubleshooting guide in documentation, Also try testing with a plain WordPress theme to see if there is an issue with your theme.
Yeah, Google instructions are the worse! That is why we have written and rewritten documentation and why the developer wrote more than one article. Not only that but their instructions and terms and conditions keep changing. People get angry at the plugin updates sometimes and even write horrid reviews based on the fact that they have had to update versions or because they cant figure out the Google API key
Thanks for providing this update and letting us know the patch worked and also about the API. If you found the support here useful or responsive and have a few seconds and could leave us a stellar review it would be much appreciated! If you do not believe the support was helpful or timely , please send us a note via the support form.
YAY!
@ jms So it wasnt Google, it was changes to WP in combo possibly with SLP 5.0.1 . Please update SLP to version 5.0.3 test it and let us know. I tested with special character on my own site and a result came back with a pin on the Map.
My test,]
I have locations on a speaaret page that is only Costa Rica, it returned results around Cordoba Costa Rica with the word typed with accents. I then tested it on my locations list page with the accent and it returned the Google MAP view for Cordoba Spain
See attached scrreenshot
Pianai et al,
I think Lances fix to how WP was handling spaces and characters may fix your issue. I just tested on my site and searched “Malmö and it came back with correct location in Sweden.
Update SLP to version 5.03
Catherine, an issue was found, but I do not know if it is your issue or not without more info. If a space was in the name or address WP treated the javascript url differently then what it used to do. We are not sure if it is a combo of SLP 5.0.1 and WP versions 5.0 etc ,
But there is a version SLP 5.0.3 that fixes the address lookup if there is a space or comma .
Please provide specifics and your plugin environment if you are still having a problem
Christian,
The developer just found an issue with the way WP changed the ouput when spaces and commas included.
Update to version SLP 5.0.3 and that should fix the spaces in your address, I just tested on my site and it works. There is also an update coming for Premier.
Let us know if that fixed the “name as all one word ” issue .
The developer has been looking into the ADDRESS SEARCH ISSUE when spaces present
what version of WP are you on? It seems there was a change in WP that changed the way spaces were applied creating an issue in SLP 5.0.1 — may have been introduced with WordPress 5.0 and the 4.9.9 patches… but not sure…
But it impacts any address a user types in with extra spaces on the map address lookukp.
A new version of SLP 5.0.3 should fix the spaces look up. I just updated on my test site and tested it and returned the correct location I had added as a test:
Scarborough, ON M1K 5J7, Canada
Just as an update. See the latest news article. Also have been checking the Google support issue tracker to see when they are going to fess up or fix their latest guffaws. Google admits to their geocoding and other errors when using the APIs and then provides a canned response….
See Issue trackers in Google API support
It appears another Google customer also reported to Google Support specifically about Canadian zip codes. And Google has assigned in support. We believe that now that Google is charging for the use of their Maps APIs and geocoding a lot more people have started reporting. if you look under issues you will see a ton of issues reported to Google and quite a few in apst month.
Hi,
Please refer to the posting guidelines and provide versions site url where using locator etc. Please note, that unless you are using Experience addon or premier and have features with additional search enhancements, such as auto complete, discrete filters, country guesses. the search and results are 100% dependent on the Google Javascript API . Even with some of our search enhancements there is no getting around whatever Google did recently with all their Javascript API look up by address. and it is not the same as their commercial maps (refer to the article link below)
Currently SLP passes address-specific lookups directly to Google and it uses your JavaScript API. In the past this has worked well but Google clearly has changed something recently that has made that service far less reliable.
Google has changed (broken) their address lookup service that nearly every map services provider uses . The developer is working on a way to fix or surpass google with his MYSLP platform. My Store Locator Plus® searches additional databases. read below article
Other ways Google has been changing their APIs
Since every site using Google MAPs JAVASCRIPT APIS is now being charged via credit card , assuming you have obtained your maps API (I do not know, you didn’t provide your web site or info, see posting guidelines) they have included support.
We have been investigating these type of reports that started springing up recently, and not as a result of anything changed in SLP. the issue is a Google Maps JavaScript API problem. WPSLP passes address-specific lookups directly to Google via their JavaScript API.Google clearly has changed something recently that has made that service far less reliable. Google has changed (broken) their address lookup service that nearly every map services provider uses — including Store Locator Plus and MySLP . Thankfully we can address that issue with the SaaS MySLP alternative with a short-term “fill in the blanks” solution and are working on a better alternative to Google Maps as part of our long term strategy to make the MySLP service better for our customers.
Unfortunately we cannot solve this issue in the WordPress SLP self managed do it yourself plugin since the site owners obtain the Maps Javascirot API key directly from Google who charges you.
Since Google now charges every single customer and every single site that uses their Maps JAVASCRIPT API and geocoding API our educated guess is this change has been part of their plan all along. In g=fact we found some articles about this posted by a marketing company that Google had a july 2018 summit where they discussed this marketing via Maps and GPS campaign. Google changed their terms and conditions and require a credit card and accoiunt for every single site using their MAPS . No more grandfathered in. You would think they would improve the searches with so many customers now paying them every month. We believe they are now introducing blatant non look up of address specific locations to boost their paid advertising campaign. Either that or they added a bug by changing towards that end.
Either way, as a customer of google API you have every right to complain or ask their support when an address lookup doesn’t work. Look up by city or name and also by zip code seems to still work fine,.
Unfortunately Google determines the results, it doesnt always just search by using the . map domain in SLP) That is not always the case. (Our News article from developer about this)
c Additional info on how the Search works
If you have the Experience add-on or Premier subscription you can influence the search and add the shortcode to append AU or have discrete search . with Premier we have added search enhancements as a work around , i.e show country guesses etc .
We have seen this issue in the past with Google searches, especially for Australia, instead of using the Google AU search engine, Google was using “international” . The map domain influences the map search but does not restrict it. MYSLP has data search engine to work around Googles inaccuracies. Many of our WPSLP customers find MYSLP to be a better work around
Piani, The message could not locate this address is being returned by Google itself. Looking at the various codex and issues with WP and trying it in Google commercial maps (no issue) and then using the special characters with the API search my guess is it is yet another issue that Google has introduced.
I will run the theory by Lance so dont quote me. But since you are now paying Google directly to use their Google API now, it wouldn’t hurt if you would send the query to their support as well.
Ok, Thats not what is meant by the Plugin environment, that view shows your plugins but not versions of SLP, addons, WP.
the Plugin environment and info needed.
double check your csv file. you mentioned you exported. When you export each location line now has sl_id. If you are not updating that precise exact id that was assigned then you would delete that column.
The sl_id has to be exact and it can change. If you are adding new locations and you want to update you need to click on what to do with the csv file duplicate add, skip , etc. it is a setting under the Import function.
Info on the headers for the woo-commerce fields and how to associate the sku here:
https://docs.storelocatorplus.com/blog/associating-woocommerce-products-with-locations/