Forum Replies Created
-
Posts
-
Premier URL controls were expanded and added over the past few years as far as I know. if you had legacy add-ons that from 4 or 5 years ago I do not have that information available. There have been many updates over the past 5 years . You can check the Changelogs under the products on the home page that may help you. or the news feeds , this news feed from 2017 describes the capability If you were able to get around it with just Power and Experience add-on, perhaps I am not understanding the functionality you are referring to.
https://www.storelocatorplus.com/version-4-7-9-allows-location-highlighting-via-url/
Ok, No Problem. As mentioned this is not a plugin issue. The developer has written a few articles about the rest api but the later versions/updates of WP fixed the issue., what you are describing is preventing communication, but this is out of my realm and will require vetting by your team with the help of the WordPress developer community at large and Sucuri.
I will close the topic
Please read the Posting guidelines and provide the information requested, i.e your plugin environment (see what is meant by plugin environment), without that info we cannot help you.
The allow addy in Url features you are referring to requires you to have Premier subscription. You bought two stand alone add-ons back in 2017, not Premier subscription so you never had that feature..
See the video and info here in doc shttps://docs.storelocatorplus.com/blog/tag/url-control-description/
SLP has nothing to do with the http to https issue., The developer uses Sucuri extensively and there is absolutely no reason to have to hack anything in order to allow a plugin to communicate with the outside world if your configuration and network server is set up correctly. . If you have HTTPS on your server it should automatically route to/from i.e. — if someone goes to http:// blahyah.com it will auto-redirect
either way, if you are having to hack, you have not configured your network and web app firewall (sucuri) properly
article the developer has written that mentions Sucuri and caching
As far as our plugin , the only thing that would be effected regarding the search functionality would be if using Chrome you will not have advantage of the Location sensor aware.
Mixed content , as far as this topic, I am not sure how you are even getting that error since your site is http not https . so it does not appear to have been migrated
I would do some research especially on the WordPress support to find out how to properly configure and migrate, or check out the Sucuri blog
Arnulf, I added a location in Germany recently; and it appeared correctly without adding the br in shortcode as long as I entered something in place of the “state” field, if you do not want to modify your layout by adding the br in the shortcode try entering a comma or anything under the field “state” . It may be a solution your customer can live with for now
The error isn indicating the string is invalid as it does not follow the UTF 8 requirements
Please refer to the rules under the Import functionality, assume you imported the location? Do you have a location with that address under your SLP locations? If so is it showing as geocoded active?
I added a location in Tübingen, Germany with a full address to my site. Not only did it geocode correctly but I also had no issue with it appearing on my map when I searched by the town / city name, see my screenshot.
This indicates that it is not a problem with the SLP plugin but something in your configuration or set-up .
Make sure you have the location added correctly, add the country and postal code
Or you can also just change and add the shortcode in the results layout and save it, he may also have some other suggestions for you that would not require a purchase.
@ Arnulf
Please refer to Jorgens reply above. To change the results layout, or any of the WPSLP layouts, to add the space, etc you can use the Experience add-on
Thanks Jorgen,
Yes, it can be changed if you have the Experience add-on and you can change it in the results layout. Arnulf did not provide the information requested regarding his Plugin environment , version etc.
Thank you for providing the correct span for the layout
P.S please show a screenshot of your Plugin environment and provide a url where you are seeing that error? Are using the plugin on a NAM , i.e. multisite? I see that you downloaded the experience add-on 4 times which is a bit unusual in one day.
If you do have a Network-Active Multisite WordPress configuration , an active Premier subscription will be required
if you still need help, we will need more info (refer to the Posting guidelines)
The “expected” is indeed what you should be seeing. if you are missing ANY sub tabs then the issue is not wPSLP but another plugin. Are you using a Minify plugin such as SMUSH? Some people reported that some of the sub menu tabs were not appearing when they used that plugin,The way their plugin was written ,to minify, ,conflicts with SLP which already is compressed. https://wp.storelocatorplus.com/forums/topic/admin-section-not-allowing-me-to-click-on-anything/
If that is not the issue, did you copy or migrate your site recently? If so you may want to check your back up before you did that or may need to use the WP debugger and troubleshoot and check to see if the migration was complete and all your data tables moved over completely.
For others who may stumble upon this support and not see what you are referring to , or think this post is about the actual API keys:
Once you have that issue resolved:
Look at the examples in docs:
If you added referrer restrictions (click on that article and watch the video ) and also obtained a unique geocoding key enter that key under Google Geocoding.
Read that article it should explain to you what the two fields “Browser and geocoding keys) are. and what the difference is.
In the Docs Google API keys and WPSLP
No Problem, Hope you get it sorted out. If you click on the pop up showing on your Google Map on that site it will direct you to the Google API info for the pop up.
If you answer the questions in order:
Error Messages
This page describes the error messages that can be returned by the Maps JavaScript API. The Maps JavaScript API writes error and warning messages to the JavaScript console. Certain error conditions may also occur, which result in the display of a darkened watermarked map.
If you are NOT the website owner, there are no steps you can take to fix any of these errors. However, you may want to notify the site owner if possible.
API Key and Billing Errors:
Troubleshooting
. In order to use Google Maps Platform products, billing must be enabled on your account, and all requests must include a valid API key. The following flow will help you troubleshoot the issue.
Are you using an API key?
IF YES:
Is billing enabled on your account?
How can I check if billing is enabled on my account?
Navigate to the Google Cloud Platform Console and select the project under which your API key was created. To confirm the key is associated with the project:
Go to the Credentials section, which can be accessed from the left side bar under APIs & Services > Credentials.
Check that the API key you currently use on your website is listed. If that’s not the case, switch to a different project, and check the credentials there.
If you cannot locate the project for your API key, you may have lost access to this project. Ask others in your organization for help. If the original project cannot be located, you should:
Create a new project. This can be done by selecting New Project from the projects list, or by selecting Create Project via the Resource Manager page.
Create a new API key. This can be done on the Credentials page. Once there click Create credentials and then select API key.
Once you have located your project in the Google Cloud Platform Console, check if billing is enabled by navigating to the Billing section in the left side menu.
Just as a footnote,
I just visited your site. page for store locations on the site shown in your screenshot. You have NOT updated your Google JAVASCRIPT API projects according to Google, you are showing a “do you own this site” pop up.
That indicates that the API you obtained once upon a time is either not valid or is not associated and updated with a billing account. You really need to contact Google or click on those links and follow through with what they are advising you.
Whatever API was previously obtained by your group was most likely never updated and attached to a billing account, you need to follow the Google API links where you are seeing those error messages!!! If it was updated and you migrated the site recently, make sure you have the correct project and correct API key in the WPSLP for browser and that you are not inadvertently using an old one
Apparently someone on your end has set quotas through their Google API billing account. SLP has no insight into any sites that are using the WPSLP self managed plugin.
as an FYI: Some info our developer had to consider and vet when he wrote his subscription based (MYSLP) fully managed software,
Map views do not always align with page views by an “individual visit”.
Example: Someone can go to your site and and visit 5 pages. Web traffic will report this as one visitor but if you had a map on each of those pages that would be 5 map views.
Or the visitor goes to your where to buy page and types in 3 addresses; each time the map is drawn it is considered a map view.
Another example, a full screen map using Google’s map view counter usually counts as 2 or 3 map views.
Not to plug MYSLP specifically but with the MYSLP subscription platform , we only count each time a map update is requested from Google. MySLP uses a LESS aggressive version of the counter than Google uses.
either way, since you are referring to the WordPress SLP you own it, you manage it and you manage your own Google API keys, so best thing for you to do is talk to google and lodge any complaints with them, they offer free support now since , they charge everyone to use their maps.
Sorry I cannot be of assistance or provide an absolute explanation for your case.
You might want to peruse the SLP news feed here to see if you glean anything that might help you.
Hi Andrew, No it is not a known issue and it is not a bug as far as I know.
Not sure about your particulars, but the last time you wrote about the permalinks, Lance answered you with an extensive reply. see what he replied back in January it may shed some light (especially if you are not the same person who worked on that part of that customers WP site before. )
https://wp.storelocatorplus.com/forums/topic/store-pages-custom-changes/
I do see some errors on your site and realize you are using a lot of customization and caching
Lance wrote an article sometime ago about the caching and updating
https://www.storelocatorplus.com/how-caching-can-break-websites-after-updates/
Did this just start happening after you updated to WP 5.2/
Did you migrate your site recently?
Review the WordPress support forums. I did not update to WP 5.2 but it looks like it may have some issues.
https://wordpress.org/support/topic/read-this-first-wordpress-5-2-master-list/
Nothing in SLP would effect breaking your internal links to your pages
You can also view the Power changelog to see what changes were made. I do not see anything that would effect your SEO page links in recent updates, the last time anything to do with SEO Pages changed was Power version 5.. Make sure you still have Enable Pages turned on.
You may need to debug with WP debugger to get to the bottom of the issue
Also, there are a few other SLP plugin styles, left for red, left for blue, and other Gallery styles available for premier customers. You might want to check them out on your dev site, make sure you have a back up of your site before changing anything permanent.
examples of CSS rules that will take precedence over the built-in SLP Theme file CSS and WordPress built-in CSS. can be found on the docs page. To find the correct rules, the developer recommends using the Firefox Developer tools or Google Chrome Developer Tools to view and copy specific CSS paths.
The Docs page shows you how to change the span and css.
https://docs.storelocatorplus.com/blog/custom-css/
There are numerous articles and documentation about setting up your Google API. I do not see that error when visiting your site so cant be sure if that is your issue. But also you should update to SLP version 5.0.5 ( See changelog here under development, that was fixed in version 5.04) That may fix the issue, there was an issue with Map regions /domains not saving and defaulting to the US, make sure you have selected Australia for your Map domain under the Settings/Map functionality
I went to your site and nothing as far as Google geocoding came back when searching that suburb.
BUT
What i do see is this error
Mixed ContentThe page at ‘https://www.sloggers.com.au/store-finder/‘ was loaded over HTTPS, but requested an insecure favicon ‘http://sloggers.wpengine.com/wp-content/uploads/2015/03/favicon.jpg‘. This request has been blocked; the content must be served over HTTPS.
And that can on cause the Google API to hiccup. See Mixed Content info
You should turn on Location sensor and set the distance to a lower distance under results settings. and/or disable initial directory from results if you do not want all the locations to appear.
https://docs.storelocatorplus.com/blog/results-panel-settings/
Also you might want to turn off the cluster map markers or change the settings for it if you believe you had the correct settings to have the map and results working the way you described before upgrading. . I am not sure if you had the Power add-on before with location sensor available. but upgrading to Premier would not automatically change any of your previous settings or css. The cluster feature is however a default (turned on in Premier automatically) That feature does show the map differently.
Things that also effect the initial display are center map at, radius always on, or only after search and also the results settings , display all, etc.
Are you saying you only want Australia and New Zealand displayed and not any of the other locations you have worldwide?
no problem
Sorry, I am on vacation at the moment.. The developer provides updates via the News channels and his blog, glad you were able to find the info you needed.
If you notice that article is dated 2-017.
Announced over a year ago, DeBaat had not updated those add-ons and they were no longer compatible with store locator plus.
he has been talking about selling them on hos web site, and supporting them there,
I do not know the status. you can contact him
I cannot readily answer your question without knowing your Plugin environment (found under the SLP Info tab) , see posting guideline
Nor the example of your file header names, i.e sl_store, sl_address,sl_city csv file examples
If it imports some lines and not others then most likely there is an issue with your csv file format.
Review the multiple pages in documentation for example troubleshooting CSV imports and CSV file headers.
