Forum Replies Created
-
Posts
-
Hi Andrew.
We do not run Apache so cannot test on it, but yes with Apache it is htaccess
Lances recent article on the issue, or the more complex article for the tech savvy people such as yourself.
(Best to test your fix on a staging or test site.)
http://lance.bio/2019/02/12/nginx-installing-wordpress-in-a-subdirectory/
When Lance has some available time I will ask him what his thoughts are.
The latest news article
https://www.storelocatorplus.com/wordpress-subdirectory-installs-and-the-rest-api/
Ok, I will notify the developer for guidance.
FYI: Under “A gallery style,” there is an inside scroll and there are a dozen plugin styles (now called locator styles) under there. I need to update the docs site a bit more to delete those old photos https://docs.storelocatorplus.com/blog/selecting-and-customizing-your-style/
Regarding what you had before in the legacy add-on plugin styles, If you need a specific type style, as a premier customer, I can ask the developer to add it when he has some time available if it isnt already under gallery style. You probably do not recall what it was called, (I know I wouldn’t), but if after looking at the additional styles you do not see one that works for you , you can contact us via the contact form and request.
under Gallery styles there is the scroll down on inside bar , for example AI Swarm, Alphaville, Bennet, Bobbitt, Brewery, default, Metropolis etc etc. Can you see them under Settings /View in the inside scroll bar under Gallery style?
see attached screenshot.
If you have Janitor you can view what is actually being used under option results layout compared to what is being shown after you change it.
I will let you know about the ifset under results when I have more info
Thanks for letting us know.
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)
Ok, that is good info. The US vs UK domain region is a bug in SLP that is being addressed, that was the only reason I was asking for info regarding if you had one so you could test the Pre release to see if that fixes the issue.
But I am now thinking, you may have the same issue we are seeing with some others who have been using SLP from back in the day before the WP REST API was used. As of SLP version 5.0 SLP now uses the WP REST API to communicate with the Google geocoder.
, after visiting your site again , when looking at the error message I see the blocked url with the word after the .com as /cms/wp json ? Do you have WP installed in a subdirectory folder, i.e
https://www.samonline.co.uk/cms/wp-json/store-locator-plus/
If so then 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 is going to use the address WordPress tells it…
So if you installed in /cms and set your “WordPress Address” to https://yourdomain.com/cms/ it is going to talk to yourdomaind.com/cms/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 /cms/wp-json/ to /wp-json instead.
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).