Forum Replies Created
-
Posts
-
Here is the retainer plan link
Hey Pete, Sorry this fell through the cracks. I have no suggestions as far as how to do it using SLP or in WP . You can write React, Vue or JSquery hack, but we do not have any specific guidance on that. If you want to tray and get on Lances schedule (he is pretty slammed) he is only doing customization projects on a retainer schedule these days.
I have no guesses /options left to explore. 🙁
If it is working on your cloned test site environment and not on your regular site, then I think you need to look into the differences there, I cannott make any inferences with the screenshot provided. It works for me, it works on your other site, so the question is,, what is the difference in plugins or server or security settings or site configuration that differentiates the two.
You can view the Import docs and see if anything jumps out at you. I.e CRON etc
https://docs.storelocatorplus.com/blog/power-import-and-wpslp/
P.S. About the import messages: Spoke to the developer and that feature was disabled in one of the updates for Power . large sites uploading large files were finding it slowed and could crash their servers because of the real estate (resources) being used within the server. Most people were not using the feature. He will take out that enable Log import and import message checkbox at some future update but he is very much involved in working with a large client at this time with focus on other priorities and customization
You dont have to worry about updating Power to 5.0.1 I am told, there will be a new version coming out. Power 5.0.1 had an attempt at a work around for the WP bug they introduced
So now I guess it may be a good idea to make sure your server is talking to Google APi etc. But you said the locations were stuck and not loading at all? or is it they are just not geocoding? if you check off the box to skip geocoding do they load?
Other then that you can send your csv file to us at Contact us as attachment in email and I can review if you want
WP 5 could be causing the issue with the import log messages, but WP version 5.0.3 fixed the CSV file upload. yes they broke that import functionality before.But you are showing that you are using WP 5.0.3 That should have fixed any import issues.
I am not sure if your site configuration is different then mine, Our developer has been
I see you are showing Power as version 5.0, there was an update, it should be 5.0.1 deactivate the SLp and Power plugin and see if you get a message to update or there is a newer update. The version under our version file was mislabeled, I just noticed that. You should have version 5.0.1 available
The issue is:
Your site made it so that the REST API on the public-facing site (front end) is disabled.
therefore SLP map (address box) cannot talk to your WP site via the REST interface to do an address lookup.
If backend geocode works (add location , it geocodes) but not the front-end it is almost always an over-zealous WP security issue. The server needs to be able to talk to the Google API to get the geocode location and return it.
Are you restricting access to your site for certain public access, such as an age restriction. We see that on some sites selling alcohol or , now medical purpose therapy etc.
If yes, your age restriction plugin/theme feature is very likely blocking all REST API requests to /wp-json…
You need to be able to turn that feature off for any of their AJAX or REST URLS.
most older plugins/themes already do that for AJAX but have not updated for REST — which is far more prevalent now with WP 5.
Ok, I did a search on the page you provided a link and using dev tools to inspect site and errors saw this error:
Uncaught ReferenceError: mtfgf_settings is not defined
at HTMLDocument.eval (eval at <anonymous> (jquery.js?ver=1.12.4:2), <anonymous>:1052:9)
at i (jquery.js?ver=1.12.4:2)
at Object.add [as done] (jquery.js?ver=1.12.4:2)
at n.fn.init.n.fn.ready (jquery.js?ver=1.12.4:2)
at a.fn.init.n.fn.init (jquery.js?ver=1.12.4:2)
at new a.fn.init (jquery-migrate.min.js?ver=1.4.1:2)
at n (jquery.js?ver=1.12.4:2)
at HTMLScriptElement.c (main.min.js?ver=1.10.25:1)
at HTMLScriptElement.dispatch (jquery.js?ver=1.12.4:3)
at HTMLScriptElement.r.handle (jquery.js?ver=1.12.4:3)
That could be an issue
To see Import messages you need to turn on messages by checking it off under General/Admin/log import messages. It shows the files that are being loaded as they load, (check off load data) but the verbiage at the bottom line as you have shown is not appearing at the moment.
I tested my site and it imported and the blue boxes showing status worked. So now I am wondering if there is an issue with your geocoding API key or something else, like communication or firewall on the server is preventing your upload.
Thank you for providing your plugin environment and screenshots.
Can you turn on the import messages and report what it is showing?
Do you have your csv file properly formatted? I,e no sl_id column if they are not replacing a current location?
looks like you disabled REST API for anyone that is not logged in
If backend geocode works (add location , it geocodes) but not the front-end it is almost always an over-zealous WP security issue.
message about the rest……WP version 5.0 caused issues when it came to the plugins that rely heavily on REST. With WordPress 5 some cannot even save pages or posts. It is riddled with REST API and JavaScript errors about invalid JSON responses. REST forbidden means your proxy server or a WP plugin is preventing REST API calls. SLP will not work — nor will any WP page/post edits.
Do not know if that is your situation or not without your site url.
If that is not the issue and you think it is the way you have set the Google API keys See the developers latest Article about the type of referrers and IP restrictions with the Google API keys.
Next Question
Tagalong, yes it will not work with current versions (or any SLP versions above 4.8.6) that was retired over the course of a 3 year process . Tagalong, proPack, and a couple of other add-ons were combined into the Power add-on. See info about Legacy. Most likely as a result of WP auto updates or updates to version 5 forced you to update SLP I assume. Now those legacy add-ons do not work. Frustrating i know but there were just too many one on add-ons and changes in the way everything is working now just required rewrites over time. See Legacy
Thanks for providing that. It shouldnt effect SLP The “deprectaaed” WooCommerce one you can probably ignore, but the other two both have to do with your theme.
Contact the theme developer and send him those PHP errors. See about Javascript and PHP issues preventing SLP to load
P.S. Turn off the debugger if you still have it on, you should never leave that alive on a production site btw.
As far as how to set up the keys ,
The developer wrote a brand new article with a video that should explain it better.
https://www.storelocatorplus.com/api-keys-with-referer-restrictions-cannot-be-used/
Hi Andrew,
For some reason Lance is having a problem with being able to reply to this post.
One question/observation….can you edit and save pages or posts WP ? If not SLP will not work. Per lance, WP 5.0 changed and is riddled with REST API and JavaScript errors and invalid JSON responses.. SLP as well as core WordPress features rely heavily on the REST API. He will be writing about this, I cannot address it, since it is out of my skill set.
You mentioned yin first post , i.e Google API you did not have any restrictions no referrers . so the news article and latest video may not effect you.
Browser Key
This should have a single restriction turned on — the referer restriction. The value of that restriction should contain your website URL. Using a wildcard like https://*.storelocatorplus.com/ is usually a good idea as many web servers allow the non-www (https://storelocatorplus.com/) and WWW address (https://www.storelocatorplus.com) to be used.
additional info about how the SLP geocoding requests , how the IP restrictions work for geocoding etc.
https://www.storelocatorplus.com/api-keys-with-referer-restrictions-cannot-be-used/
If you could send any additional questions and info to the email support so Lance can answer the more technical questiosn on the subdirectory urls etc that would be appreciated.
?? I cant see any issue on your site.
1) What is your plugin environment? Please provide a screenshot of your plugin environment
2) Are you referring to being able to add a location under SLP Locations in the back end add? Do you have some other plugin like Smush that maybe clashing with SLP? Smush or any minify plugin can be turned off. SLp already mifies and there is a conflict with that plugin.
You can try debugging on the back end. There is an Enable debug under SLP /General tab, you can enable that and then try to perform the action and see if you get back any errors. and provide the error log or ffor better results ollow the WPDEBUG instructions in the troubleshooting docs
Thx for letting me know.
I will mark as closed
We need your plugin envirnment that will also show what verion of WP you are using, as you probably are aware, WP auto updated everyones sites and broke a lot of things,
I really cant weigh in or ask the developer to weigh in when we do not have your plugin environment or additional info
P.S. The demo at the time was probably NOT updated to WP version 5.0 or higher. And that is where WP broke a lot of things.
Lance is looking into it. Something changed recently and he is trying to see if it is WP, (there auto update security patch) Google or SLP.
We are having a difficult time trying to reproduce the issues on our sites.
Did you update after backing up? If you roll back SLP to 5.0.2 for instance is there a problem?
Is this the site url with issue? https://curbtheappeal.com/#HazardousSites
Alex,
Could you provide me the exact site url where the map loads so I can visualize what you are asking?
If all your locations are in UK you can use the append feature with experience add-on and it will show the areas only in UK but it will not go back to your center map at. Once the search has initiated on the site the google geocoding API kicks in.
Just using the Map domain as UK is not going to restrict searches to just that map domain you are correct. That is not how Google works.
You can help your customers out with experience add-on by providing the discrete search function
With Premier there is a limit by territory feature but it does not sound like that is what you are looking for. There is also a boundary influences guesses, but that will not limit the locations exclusively to the data set to recenter. Other option is to limit the results radius settings and radius behavior
Thanks for letting us know. I had a 1 hour meeting this morning with the SLP developer going over various scenarios and issues others were having and yours came up as well. So i received an impromptu lesson showing me where all the restrictions went , what the difference was etc, and the fact that SLP update a few months ago works differently t no longer routes geocoding requests direct to Google. Since a few releases ago, They are now routed to your WordPress install where WordPress communicates with Google. This allows your Google API keys to be secured and not leak out via JavaScript where anyone can “borrow” your API key and install it on their site while you pay the bill. Older versions of SLP didn’t care if your WordPress REST endpoints were mis-configured because it wasn’t using them
Glad to hear that the message you were seeing was indeed because of the IP address . And no it isn’t weird about the IP address, that was going to be today’s question to you after my meeting.
, Lance was explaining to me about the cpanel and the server proxy and the different IP address…..since I am really not that technical my eyes starting glazing over.
Ok, Also the SLP Developer said if you want to send screenshots to our contact us support email. he will be able to look for you as well. Screenshots should be of
1) SLP General Settings showing both Google API Key fields.
2) Google API Key DETAILS screen for the Browser Key (showing the key ID , restriction settings, etc.)
3) Google API Key Details screen for the Geocoder key.
If you use IP Address restrictions the IP address must be the direct IP address of the server not a proxy service address. Could that be why Google is sending you the API error?
P.S. Are you on SLP version 5.03 now?
Here are some cool CSS suggestions and you can see the fields that can be changed
https://docs.storelocatorplus.com/blog/store-pages-templates-slp_pages-work/
and how to make the phone clickable and the shortcode for the SEO Pages
https://docs.storelocatorplus.com/blog/make-a-dial-link-phone-number-clickable/
More info, attributes Creating StorePages scrol down to the info for custom templates
Not sure, ,what is your plugin environment, i.e Under SLp Info? will show versions etc.
https://docs.storelocatorplus.com/blog/store-locator-plus-info-plug-environment/
Andrew,
I am at a loss but have the developer trying to figure this out. It is a lot of different errors I am seeing reported by customers but they are all related to geocoder, so I do nto know if Google changed something on us yet again or what is going on. We had a customer who fixed his API key restrictions and it wirked and now the problem is back.
Long story short, can you send , via the contact us any WP debug logs you might have if you have tried that, and/or send a temporary log-in via Support for your staging site so our developer can look at it?
Ugh so frustrating I know.
Aha, This may be very helpful to solve some of our missing locations cases. I do not know if Google has yet again changed something or what, but the developer needs as much info as possible because we cannot replicate the issue on our end. We understand people wanting to restrict the APi key, in reality the chances of everyone having the wherewithal to even be able to find your API key is very small.
Do you have a test site or a staging or dev site that you might be able to provide our developer if he needs one ? (not in the forum bu via our secure support contact us)
Aha, This may be very helpful to solve some of our missing locations cases. I do not know if Google has yet again changed something or what, but the developer needs as much info as possible because we cannot replicate the issue on our end. We understand people wanting to restrict the APi key, in reality the chances of everyone having the wherewithal to even be able to find your API key is very small.
Do you have a test site or a staging or dev site that you might be able to provide our developer if he needs one ? (not in the forum bu via our secure support contact us)