Forum Replies Created
-
Posts
-
When Posting please follow the Looking for technical support guidelines. I.e. versions, site url etc.
Because of the WP 4.8.2 auto update, the developer of SLP had to patch the code.
Please update SLP and Power to 4.8.6. SSLP never auto-updates for these reasons. See the authors news article about this unfortunate WP update.
https://www.storelocatorplus.com/updates-to-address-wordpress-4-8-2-issues/
P.S. When posting in forums, please follow the forum guidelines and provide versions etc. A screenshot of the INFO/Plugin environment under SLP works best and provides the information the developer needs if he has to debug. Also provide your page that has the site url locator on it.
Hello,
Thank you for your question. We do not have that exact style as shown in your example but you can try the directory builder with the map results layout shown as hiding the map . Otherwise it would require working with the developer as a paid customization https://wp.storelocatorplus.com/product/customization/
estimated at 2 code days plus a couple weeks to deliver. if you need it ASAP please contact us at support with specifications and details and the developer will get back with instructions and questions.
SLP version 4.8.6 was released to address the issues caused by WP 4.8.2 auto updates. Experience and Power have also been updated and released. SLP version 4.8.4 released this week fixed the issue you described, further update to 4.8.6 needed to address WP 4.8.2. See news release from the developer
https://www.storelocatorplus.com/updates-to-address-wordpress-4-8-2-issues/You can thank WP version 4.8.2 auto update for that. The developer has released a patch as a result. Update SLP and Power to latest version 4.8.6.
The WP 4.8.2 is breaking a lot of plug-ins. All in the name of “security” and the WP community is up in arms. The developer has been forced to change the Power add-on and the core SLP plug-in to 4.8.6 to address the WP changes. This means that anyone who used to use categories such as the Legacy Tagalong add-on will no longer see them and it is not something that SLP did.
See the developers article and fix here
https://www.storelocatorplus.com/updates-to-address-wordpress-4-8-2-issues/
It is under General/Server now. I will update the docs site
SLP uses PHP 7 and is tested with PHP 7. In fact most of our customers who are also developers use the php 7 version.
My personal test site,( under INFO/ Plugin environment) shows PHP Version:7.0.22-0ubuntu0.16.04.1
MySQL Version:5.6.29
I do not see any warnings.
Do you have a question specific to SLP? if so could you please provide the information regarding versions, your site url etc.
See location sensor docs for more info on how it works depending on browser and your site security
Make sure your site is backed up before attempting to download any new software updates or plug-ins. (see docs)
Next Download the latest version of the add-on from your account , it should be downloaded as a zip file to your computer. Deactivate SLP, Deactivate your add-on, delete the old version of the add-on and install the latest version of the add-on from your directory.
See docuementation
Hi Chris,
Lance sent you links to download the pre-release of EXP 4.8.4 (not to be used on live production site) He could not send to you as attachments, we tried a few times but delivery got bounced back due to size or mail server proxy not allowing attachments on your end.
Thanks for your patience, sorry for the delay. A lot going on including hurricanes. 🙁
Do you have a back-up of your site? Assume since you jumped from WP pre version 4 that you may have other plug-ins that are outdated and not using the jquery versions required by WP or are breaking javascript.
“The Store Locator Plus map is a very visible indicator that something is wrong with the JavaScript on your site. It is often the first thing you will notice. Often the problem is not with the Store Locator Plus code. Since the SLP plugin cannot control if its JavaScript is run first or last there is a high likelihood that some other broken JavaScript runs before it. When that happens and there is a fatal error in the other code ALL the scripts stop running on the page, including the SLP JavaScript. That means the SLP script won’t talk to Google and that means Google won’t get the request to load the map tiles.”
Jumping multiple versions if never recommended. Try using the WP debugger (see docs) to try and isolate the problems.
You would not need to obtain a new Google API key unless you have changed the domain IP address
You need to start a new thread since this is no longer “categories” I will split, we have mentioned about starting new threads in our podting guidelines. Also a 500 error is not conclusive , it is usually as a result of your internal server.
Thanks for providing this info Elizabeth, I have asked the developer to look into it into it since , as you mentioned it is a WP generated issue and it may effect other areas in coding.
If you could Provide a screen shot I can ask the developer to look at it. I edited one of my locations with an ampersand and when I went back in the back end it was showing & as if it was in html but I was not getting any error messages. that would not be anything from the add-ons but part of the basic SLP core so I would need to see what you are seeing ti get his take on it. Thanks
Have you tried clearing your cache to get rid of any errors and reloading? Could you provide a screen shot?
Are you referring to the back end admin location panel, or the front end? Viewing your “site location” I do not see any issues when I search by Postal code.
If it is the back-end look at your Display options, if it is your front end, it is most likely is your theme or some special css that is not in the correct format. See under documentation themes, Troubleshooting , generating Store Pages, and Locator Styles
P.S. You only need a Google API if your site starting using maps after June 2016 or if you changed domains
To assist you we would need the information regarding your Plugin environment as stated in the Posting guidelines.
For instance do you have any add-ons?
It appears that the problem maybe with your theme and which SLP Gallery style you chose, or didn’t choose. Error failure being shown here.
http://smilingmoosedeli.com/smd-wp/wp-content/themes/the-moose/css/bootstrap.css.map
There is a troubleshooting guide in our documentation. See the info under Grey Map or Map not loading
Please provide the information so that we may assist you, i.e. Versions, Site Url that the locator page is on and your Plug-in environment.
The information required to assist you is outlined in the read Before Posting Guidelines.
Hi,
The SLP styles now have Gallery styles inherent with the new add-ons. you can still use the older styles. look under the View tab and the A Gallery style drop down menu to select an older plug-in style you may have used before. You can then use the same CSS you had before. If you have a particular style you would like, please write to support and the developer can look at creating one for you when he has some downtime or if it is an easy update.
Some documentation and videos that may help you.
https://docs.storelocatorplus.com/blog/adjust-locator-styling/
https://docs.storelocatorplus.com/blog/layout-shortcode-cheat-sheet/
https://docs.storelocatorplus.com/blog/selecting-and-customizing-your-style/
First, your versions are not updated to latest releases of SLP
Second: Check your theme CSS , it appears that the grey bulb is showing the “center of the map”, i.e what Google thinks is the center of the US. , so yes it may be a home marker if you do not have Locate sensor turned on and you have hide radius
Third : Your web site has warning about mixed content. Your icons are under http but your site is https
Mixed Content: The page at ‘https://pulsecenters.com/locate/’ was loaded over HTTPS, but requested an insecure image ‘http://pulsecenters.com/wp-content/plugins/store-locator-le/images/icons/bulb_azure.png’. This content should also be served over HTTPS.
(index):1 Mixed Content: The page at ‘https://pulsecenters.com/locate/’ was loaded over HTTPS, but requested an insecure image ‘http://162.144.204.20/~pulsecen/micro/wp-content/plugins/store-locator-le/images/icons/bulb_azure.png’. This content should also be served over HTTPS.
(index):1 Mixed Content: The page at ‘https://pulsecenters.com/locate/’ was loaded over HTTPS, but requested an insecure image ‘http://162.144.204.20/~pulsecen/micro/pulsecenters/wp-content/plugins/store-locator-le/images/icons/bulb_azure.png’. This content should also be served over HTTPS.
Lance has looked into it and I think he communicated with one of you, not sure, but he believes he has fixed it with SLP 4.8.3.
His answer to the bug
“The issue is related to the translation strings and how SLP is creating the HTML element structure. It is using translated names for div IDs which is breaking the new JavaScript-based editor. It will require a patch to resolve this in SLP. Not sure how long this bug has been in the code, but it never had an impact until we started modernizing the interface to newer JavaScript and HTML 5 standards. ”
COuld you guys update to 4.8.3 and see if that fixed your issue?
General / Data /Enable Pages. To use the SEO Pages you must first “enable Pages” under this setting.
P.S.. I notice on your screenshot you provided that the directions column are cut off. But when I just checked again and used the password and searched by zip with using 60 miles the map appeared without a problem Assume you fixed it?
