Forum Replies Created
-
Posts
-
Hello Arthur
Could you provide us with additional information?
Versions, Plug-in environment etc. I do not see any orders for the Power or Experience add-on under your name. I searched the site that may be what you are referring to fill station? I do not see the version of the Power add-on.
Did you deactivate /uninstall SLP and add-ons and replace them with the latest version?
You might want to uninstall the plugin and reinstall.
I cannot tell if there is an issue with plug-ins or if you have javascript or jquery errors.
Dan,
Thanks for letting me know. There shouldn’t be any issues going forward. Please et us know either here or through our contact support link.
Wes,
The latest version of the Premier plug-in is now in Production all versions as listed here. Please let us know if you have any issues with the updates.
Wes,
Can you get back in the WP admin and delete the premier plug-in. There was an error with the last migration which needs to check /disable against older versions of the plug-ins with premier.
The later version of Premier has not been published.
All your versions should be 2210.xx
P.S. There is a PRE RELEASE version of Premier that is a higher version. I see that it has not been Published to Production and have notified the developer to fix it asap.
Dan,
The base plug-in was not listed in WordPress for a while but that was rectified. The support for the plugins and add-ons have always been supported.
In the meantime I have done some sleuthing on my test site and have reported the issue to the developer. He has been changing a lot of things in the back end and the migration didn’t set to check for the old Premier plugins.
The developer says try this in the meantime.
Deactivate all the plugins and add-ons
REMOVE Premier plugin (delete it) from WP admin panel.May be safest to remove Experience and Power as well.
Then upgrade SLP and then upload/activate the latest version of each plugin.
The latest version of SLP
Side Note
Please make sure to provide us the Info /Plugin environment which shows us your versions and also what PHP version you are using.
The software has been tested for PHP 8. Which is the latest supported by WP. We are not updating to PHP 8.1
Wes,
I cannot replicate your issue.
Did you follow the update process recommended by WordPress and SLP?
Make sure you have a backup copy of the current version of SLP you have installed that IS working with your add on packs. We ALWAYS recommend that your site uses VaultPress or JetPack
Whenever you update the base plugin make sure ALL of your SLP add-on packs are updated to the latest version.
Upgrading An Add-On Pack
Before upgrading make sure you have a backup and easily-accessible copy of your Store Locator Plus base plugin and add-on packs.
We strongly recommend looking into the WordPress backup, or better option Jet Pack. One of the features included , besides real-time incremental backups of your site with restore points, is the ability to restore the site to an alternate site
This should be standard practice before upgrading ANYTHING on your site including WordPress itself.
First upgrade the base plugin. If there is a newer version of Store Locator Plus available it will show up here. Otherwise Purchase and download it from the SLP Storefront. Install the plugin via the instructions below.
If there are any SLP add-on packs available they should show up on the upgrade list, however the WordPress hooks that query remote servers do not always respond fast enough to notify you when a non-WordPress-hosted add-on pack has an upgrade available.
Follow these steps to manually upgrade SLP or your add-on packs:
- Go to your WordPress admin panel plugins page. Compare your installed versions to those listed.
- Login to your account on the Store Locator Plus website.
- Download your plug-in and add-on packs.
- Via your WordPress admin panel, deactivate and delete the outdated version.
- Via your WordPress admin panel, install the zip files you downloaded from the Store Locator Plus site, activate the add-on packs.
Hello Shaye,
Could you provide your plug-in information. We need your versions etc. It appears you are not using the latest version of the plug-in.
Other suggestions is check your Search and Results settings. Make sure you have correct display settings under results.
I do not see anything in your browser as far as errors and I cannot reproduce the issue
Hello,
Have you added the Google MAP API key and turned on billing?
I think you would benefit from converting over to the SLP SaaS solution .
Just click on one of the plans here
There are plans starting at $5 a month. If you need to import or have over 125 locations the Professional level would be the right level plan for you.
The advantages for you:
NO dealing with the GOOGLE API keys…we do that.
No dealing with the Google BILLING …we do that.
No need to do troubleshooting, we offer responsive support.
COPY and Paste embed script on multiple sites.
Why do you have to block Google MAPS? With the Power add-on you can use Location sensor and the visitor would then click on Allow or not. That would alleviate your policy issue I assume. We have not had any of our European customers say they have to block Google Maps
You do have an error on that page with the “slideshow” not being present. Error message Failed to load resource: the server responded with a status of 404 ().https://naturverbund.de/vendor/assets/uikit/js/components/slideshow-fx.min.js?ver=6.0.2 Could prevents the page from loading
Blocking javascript will break SLP.
https://storelocatorplus.com/good-javascript-code-critical-locator/
The latest releases for SLP versions
fixed the trash barrel issue, the Power issue of labels missing and some other bugs. The change Log and News will be posted by the developer.
As always:
Please make sure you have a back up before updating any new versions of any plugins or Word Press.
Hi Mic
Yes the developer published the releases last night. For Both the SLP Base plugin and the Power plugin.
It should be ok to download updates from your Plugin admin panel now.
@ Mick AKA Amanda…
I sent you the pre release zip files but they are not making it through your email firewall
Hi Shaun,
Not sure which update started it but most likely the latest . So many things had to be addressed and stripped out and re worked in order to have WordPress re list SLP in the directory. The developer has a few updates in the works now. One for the SLP plug-in and another for the Power plug-in (that is going to have a new Reports feature that had stopped working as expected) . I am in the middle of testing them . Any of our Premier customers can download the Pre releases versions to test on a cloned or staging site. Or can try and send any willing customers the zip file if their email provider allows it.
We are hoping to have the updates out by the end of the week if all goes well.
Yes they are, we just tested our latest . Here is an article from the developer concerning the PHP and patches
Which version of SLP are you using?
@Amanda, AKA Mick
I split this topic off because it is a separate issue that I wanted to test. I found that using the “Trash barrel” does not delete the locations. But if you check the box and then use BULK actions to delete permanently that works. I am not sure why this is the case, above my pay grade, but I will add this to a bug report as a non critical fix needed.
See the screen shot
@amanda
I checked both SLP Version 5.13.8 and SLP version 15.14 and the delete functionality is working. There was an issue in a prior release where that was fixed.
Is your client using the trash baskets on individual one at a time, or using the Bulk actions /delete permanently method?
I tested both and they are fine. I refreshed and the ones I deleted are gone. So if you could check if they are using an old version that would be great …You can see the changelings and SVN repository in the SLP WordPress directory
Yes, I am testing the Power pre release beta now that should fix those labels as well as a couple of other issues.
the delete and having it re appear sounds vaguely familiar with an older version that since was fixed, I thought…I will have to check the bugs report in our new reporting system to refresh my memory. Is that customer also using the latest versions?
If you have a test site and or a Premier account you can download the Power pre release , it also has fixes and new reporting interface. If you do not have Premier but want to help us test it I can send you a Pre release version for use only on a backed up test site . If you are interested send an email to support.
Mick,
Thank you for the thorough explanation. I hate to say it but I totally forgot about those fields. I am wondering if the latest WordPress update caused the issue since I am comparing the previous versions of the PLUG In as well as our new releases. The developer found a lot of issues with the Last WP update that effected layouts. I am going to sk him if we can roll back on of our test sites to earlier WP versions
I will keep you posted
Mick,
Thank you for the thorough explanation. I hate to say it but I totally forgot about those fields. I am wondering if the latest WordPress update caused the issue since I am comparing the previous versions of the PLUG In as well as our new releases. The developer found a lot of issues with the Last WP update that effected layouts. I am going to sk him if we can roll back on of our test sites to earlier WP versions
I will keep you posted
Amanda , I am texting the Pre release for SLP and Power and it appears that the formatting bug has been addressed in the next release which we are expecting to have out this weekend, fingers crossed. !
I think this is a formatting issue as mentioned above and I am identifying it to the developer to fix this ASAP with our next release. Thank you for bringing to our attention…but if you could try Chrome and confirm I would really appreciate it
Hello Amanada,
I do not understand the screenshot you are showing me. What Power extended fields are you referring to?
Could you tell me which browser you are using when you load or edit locations? I see that when I use Safari there seems to be an issue the way the back end appears as I opposed to Chrome. If this is the case for you I need to notify the developers since the previous releases were tested for that and fixed, but if it is a recurring bug they will have to delve into further
Example of Others reporting bad addresses using the Google API can be found in
issue tracker.
https://issuetracker.google.com/issues/159562012
Yep, I see that. That is most likely a Google problem. Which is why you see the message ” Could not locate this address. Please try a different location.”
Since you are using the Plug-in version and managing your own Google API keys, they need to provide you support as to why they have decided today not to recognize that zip code for Beverly Hills. Or you can try turning on Show Address Guess to try and circumvent Google if you have a Premier subscription. This article by the developer can shed more light on how Google has different data sets and algorithms for their commercial MapsP.S. I looked at your site since you did not provide us with your Plug-in environment and I see the versions you are using can be updated for your account. See versions