Forum Replies Created
-
Posts
-
You didnt mention what version you had of SLP. The geocoding methodology changed in version 5. Refer to the changelog here
There was a reason why SLP was changed to have the communication go through the WP REST API instead of direct to Google. Going thru the WP REST API added Security. This prevents others from stealing your geocoding key so that it is not visible to the public . Too many of our customers do not know how to add IP restrictions and obtain the separate geocoding key.
Our developer has been researching to see if he can create a work around but after researching further he realized that sites set up with configuration using the old Codex docs and not the WP Developers handbook may not have their site configuration to use REST API set up correctly. . I am not sure how much time he is going to be able to invest to address customers with the specific issue. He will be writing an article about it for the tech savvy people such as yourself and how you can add the rules.
As I am not as tech savvy and am the go between for the lay person who is our regular customer base, bear with me with the explanation.
the issue is “– the web server configuration, regardless of which web server you choose, is NOT correctly re-routing requests to the URL that WordPress is “listening on”.
SLP now uses the address WordPress tells it…
So if you installed in /wordpress and set your “WordPress Address” to http://yourdomain.com/wordpress/ it is going to talk to yourdomaind.com/wordpress/wp-json/
If WordPress is not responding to REST requests there then you must add a rule to your web config to say “hey, re-route all requests coming in at /wordpress/wp-json/ to /wp-json instead.
The SLP developer will write an article on this issue but will not be re-writing an option immediately. . In the meantime you can add an additional rule for REST API requests to make sure they get routed correctly. (hosting companies allow users to adjust this)
Those sites that have installed WordPress in a subdirectory , somehow the REST API in WP is effected. Regular WordPress installs does not create the issue.
Version 5.0.4 beta pre release is being tested to fix the domain issue of always pointing to the US. We can send the beta pre release if you have a dev site or testing or staging site to try it on. Please write to us so we can send the Pre release to you.
Premier subscribers always have the beta versions available. We do not mind providing the pre releases but just want to make sure you know they arent fully tested and thus encourage people who have a staging site back up (JetPack provides the ability to have a staginmg site btw)
send email to Contact us and request SLP version 5.0.4. beta pre release
There is a beta version out that addresses the map domains always pointing to US but it doesnt sound like that is your issue since the issue is the WP REST API in subdirectory even though they tell you you can do that, . If you have a dev or staging site we can send the pre-release.
The developer has been researching and researching and the problem is in URL routing of the REST requests — it isn’t getting to SLP validate the connection
if he hacks his code to work with WP in a subdirectory he is afraid that sites that are NOT having WordPress installs in a subdirectry will now break. he started routing the Geocode requests using the WP REST API back in October. no problem on the majority of sites. It seems that people started updating SLP to version 5 and if they had WP installed in subdirectory now it breaks. If you could provide us info , did you upgrade from SLP version 4.9.x to 5 or 5.03 recently or did you update WP to 5.0.3 and then the errors began?
Can you downgrade to earlier version 4.9 to see if that corrects the issue? The development downloads and earlier versions can be found here
https://wordpress.org/plugins/store-locator-le/advanced/
In other words:
There is no JSON listener (WordPress REST API) there.
The console error is showing their url with the WORD wordpress. Thats wrong
http://www.pomonapectin.com/wordpress/wp-json/store-locator-plus/v2/geocode/c54591d26325c3ca3f9e82d371265dfd/us/United%20States
The developer wrote this article about the json and REST API
https://www.storelocatorplus.com/address-lookup-failures-on-wpslp/
If you do not find a plugin style that meets your needs and want to further modify the results layout you would need the Experience add-on
and have basic knowledge of CSS, and HTML.
See documentation
and data field
Please when posting provide your plugin environment.
Please refer to the posting guidelines. It might be possible you have the exact same issue , configuration, referreres, API keys, add-ons, other plugins, WP version, map domain (he is UK map) etc as William, but most likely your back end isn’t exactly the same.
I realize the message returning is the same exact message but It is basically saying cant talk to Google and they are not talking to us so no location is found..
If you could , please start a new post. following the guidelines and provide a screenshot of your WPSLP plugin environment.
If you have no referrer you only need the one key. The browser key. Do not add the browser Google Maps API key in both fields. If you do restrict follow the directions that Lance provided in his articles. This one also has a video to explain it.
https://www.storelocatorplus.com/api-keys-with-referer-restrictions-cannot-be-used/
Did you migrate your site from http to https? Is your cert valid in Googles eyes? I am still seeing the error:
Secondly, as far as what we are seeing that the domain is poiting to US even if you have selected the map domain UK. There is a pacth being tested. We can provide you the pre-release via email if you have a staging site, a clone or dev or test site.
Make sure you always have site back-ups.
We may have a fix for the domain issue returning US even if you put in UK,
if you want to test the pre release version 5.0.4 we can send that to you via email, but it should only be tested on a dev or staging site if you have one.
It may not fix your 404 error but it should fix the map domain issue. You can send request to contact us for pre release version
The developer is also revisiting the function setting the map domains. He thinks there may have been an error when he fixed the “map region” in a previous version. We need to test the new SLP release and will let you know. If you want to test it (if you have a staging or dev site to test on) we can send you a pre release via email.
Let us know if you have s somewhere to test the slp 5.0.4.04 beta
P.S. when you do inspect and go to the link for the error shown in the browser window you will see this
If ProPack is not active it will not show up in your Plugin environment , ditto with Extended Manager, (If this is an exact screenshot of your current plugin environment)
You have a json error. And the regions search is US (not UK or GR)
Use any Browser dev tool and inspect your site you will see under Console this error
Failed to load resource: the server responded with a status of 404 (Not Found)
And more specifically if you use the Browser tools and inspect the Network:
Please read the Developers article about your referrer and restrictions
your site is not able to freely communicate back and forth between WordPress, , Google etc.
Your REST API is blocked for some reason
HTTP/1.1 404 Not Found
Date: Fri, 08 Feb 2019 19:37:02 GMT
Server: Apache/2.4.37 (cPanel) OpenSSL/1.0.2q mod_bwlimited/1.4
X-Powered-By: PHP/7.1.26
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Link: <https://www.samonline.co.uk/wp-json/>; rel=”https://api.w.org/”
Vary: Accept-Encoding,User-Agent
Content-Encoding: gzip
Content-Length: 12770
Connection: close
Content-Type: text/html; charset=UTF-8
Glad it worked out for you
Importing does not “remove stores” There is a function under locations bulk actions called delete permanently.
You should make sure you have a back up of your site.
You can export your locations download to a csv file. (Some docs, about large exports configuration etc and export to csv file)
You can them delete. You do not show us your plugin environment so I do not know if you have the Power add-on. You need the Power add-on to export/import
You can make changes and under the import function choose how to handle duplicate . Review the notes on the sl_id column. You should not use that header on reimports unless you are using exact same sl_id in the locations datainfo)
here is the documentation about Duplicate handling.
No idea, but Google has always been constantly changing the algorithms. Example as explained by the developer, Google moved Kansas City
ProPack and SEO Pages have not been active plugins for at least two years. You have Premier, you should be using POWER add-on. I see that someone has SLP 9999999 DO NOT UPDATE!! on your site. Ditto with POWER add-on
Someone sent an email in as well, and the WP version there was 5.0.3, PHP is 7.xxxx and the SLP would need to be updated and ditto the Power to work with your current version of WP.
The SEO Pages and ProPack and enhanced add-ons should be deactivated. I am not sure why you are showing those, what kind of issues on your site that would warrant you to keep old plugin and add-ons since you bought Premier and are also showing Power.
We do not support SEO Pages version 4.1, etc. that has not been on that version for over three years.
We cannot provide specific suggestions for this since the SLP plugin uses the built-in WordPress rest_url() method which breaks some sites with “unique” (non-stanard configurations).
Unfortunately, without additional settings such as an append search Goolge is going to return what they think is meant by kettering should be Kettering ohio.
They need more information then just a word if there are more then one location in the world that can have a specific search associated with it. They will return the best option in their opinion. The only work around to what Google is going to guess that we have are search enhancement option in Premier subscription or the Enterprise level plan in MYSLP. In MYSLP we can add Kettering to the database with a lat and long to return and it would search the dataset in MYSLP first.
But with the WPSLP free plugin you are at the mercy of google. If you do not think Append is viable for you, then what about discrete searches?
I am not trying to sell you something you do not need, but all the plugins that require Google MAPs APIs are limited to what Google will return and a lot of man hours have been put into the addons by developers to try and work around the google limitations and interpretation of what to return with their millions of algorithms which change on a regular basis (see article the developer recently posted about Google tweaking algorithms and in essence Moving Kansas City..
Thank you. This is a question for Google support. Now that everyone who has their own MAPS Javascript API key has to pay Google they offer support. Not sure how useful the support will be but you can ask them why and what domain to use. I do not see any results being displayed under your map when it loads, do you have results Show locations checked off, or disabled until search?
on my site, I have Experience add on and use the shortcode append search for my Australia Map. And that resolves the issue. Without the append or shortcode with the country region then you are at the mercy of Google. it is not a failure of SLP.
If you want better results we could suggest using MYSLP.
With MYSLP you merely embed a script, you do not need to worry about the Google APIs.
Please review the documentation for information. I think you are confusing the no results found, and the various settings.
Looking at your site, You have chosen not to show any results when the page loads, If you believe the search is the issue, try these troubleshooting suggestions to see if you have a conflict with abother plugin, javascript or theme
https://docs.storelocatorplus.com/blog/q-i-see-a-gray-map-or-blank-map-and-search-does-not-work/
it appears on that site that you do not wish to have any results showing, or your theme is overriding some of the elements. I would try changing your theme etc on a staging site and see if you are still having all these issues.
as far as No results found, In your results setting what do you have for settings under: AFTER SEARCH Number To Show?
I am afraid I have run out of suggestions and cannot replicate the exact issue that you are seeing. So the best thing would be for you to try some of the troubleshooting suggestions
Could you provide your SLP plugin environment so we know what versions of WP and SLP and premier and the Plugin addons you are using (refer to the posting guideline)
Also which plugin style are you using?
Ifset should work in results layout but the plugin style can also dictate some settings
. the Bubble layout info needed
I do not see any errors off hand . Was it working before updating WordPress? we could look into it further if we knew what versions and plugin environment you have.
What version are you using? Did you deactivate your SLP plugin and all the add-ons? I see you signed up for a new Premier subscription. Are you trying to update from an older version of the plugins? What version of WP are you using.?
Please see the steps to upgrade , activate in Docs and/or if you have skipped and can’t auto upload or activate see Manual updates in news blog
I revisited the sites . You do not have your site or SLP set up correctly. Are you asking about the WordPress SLP plugin? or MYSLP?
Provide a screenshot of your SLP plugin environment as requested in posting guidelines and explained here.
https://docs.storelocatorplus.com/blog/store-locator-plus-info-plug-environment/
Without your plugin environment I cannot help you.
Both of your sites shows the url to the source map doesn’t exist.You can see the issue using any browser dev tools and see the error
Source map error: request failed with status 404 Resource URL: https://3v718p3kg0df2fduqn2yrgeg-wpengine.netdna-ssl.com/wp-content/plugins/store-locator-le/css/twentyfifteen_rev03.css
Refer to the latest developers info on the news page for this, he also has included a tutorial video.
https://www.storelocatorplus.com/api-keys-with-referer-restrictions-cannot-be-used/
You do not need the geocoding key as a separate API key, if you are not restricting.
In addition you have many other errors all about those keys. you should not be adding the “url ” in the browser key field in SLP but the actual key . I am not sure I follow you on that one.
Your theme may also be using or trying to load API, you can try a plain vanilla WordPress theme. If you need overall help with your WordPress environment and need the developer to assist you one on one , there is a retainer plan through cybersprocket.
I am sort of baffled as to how anything is working with that version of SLP. You have Premier subscription which means you have Power, add-on available to download which replaced ProPack and Tagalong quite a while ago. Are you keeping those alive because of your PHP version? we no longer support either of those plugins.
SLP is on version 5.0.3, etc etc. (see updating and where to find0 We have not supported proPack since WP version 4.8 and SLP version 4.8.2. WordPress auto updated everyone to version 4.9.9 as you are showing. WP version 4.9.9 broke the ability to import csv. See the developers post here
They fixed the bug that they introduced with WP version 5.0.3 .
Make sure before you update or do anything you have a site backup.