Forum Replies Created
-
Posts
-
Hello Jim,
I see the Premier in your account.
The back end admin menu section of SLP has changed a bit since you first intimated and installed on your sites. Pages is under OPTIONS /APP now.
I do see that it is preventing an edit of individual pages. My guess is it has changed with the Word Press 6.4 updates since you and I are seeing a message WordPress error. I know we were having an issue with categories that was fixed with the last power update that became broken with the 6.4 update.
Looking at permissions reports in the WordPress tickets it looks like that is or was a problem identified with 6.4 and someone responded a conflict with Polylang
Thank you for reporting this to us, I cannot dive further into it at the moment, our developer is on a long awaited holiday.
But I will definitely put this on the radar
To help us delve into this please provide versions of WP etc that you are using on the new site . Go to the SLP plugin and open INFO/ right hand side Environment tab and take a screenshot
Also , I see pages are working on production . Are you using a different WP version in your production site?
There are new updates for the base Plug-in and the power and other add-ons. Let us know if your issue is resolved
The developer is working on Updates over the weekend. The INFO Tab will be fixed, we are testing updates to Power. Thanks for reaching out and reporting the issues and working with us to resolve.
You can download the updated version of SLP and the Add-ons 2506.18 and try exporting your list now.
Hi,
Yes you can try on your staging site. You are correct never put beta releases on a production site. We have been testing the versions 2506.18.01 and those are stable.
As far as the other pre releases, I am checking with the developer as far as the BETA pre release of Power 2506.18.02
I received an error .
Use the production versions on your staging site please and report back to us if you see any major issues.
There is one minor issue that will be resolved in the next Power update and that is the category check box sticking.
Thanks for your patience
P.S. Make sure your base plug-in is also current 2505.12
Did you update the base locator plug in as well as the power Plug-in?
What version of the plug-ins show in your admin page?
Power is 2504.30
EXP 2505.14
If those aren’t what you have log into your account and download the add-ons zip file.
Also if you provide the clients name we would be able to see what they have in their account
Manually deactivate them
The link to the downloads page for Premier customers has been fixed. You should be all set now.
Thank you for contacting support and bringing this to our attention. Yes there was a recent up date to the plug-in and the add-ons that should have been published/ loaded into Production .
They will reach out to the developer to make sure this happens
That order was made originally under a different account name. Make sure you are logging into the correct account since the account owners name and email is shown as Morgan . So you may need to contact them for the access.
You had multiple accounts under your own name but they were cancelled.
I do see all the downloads available on the Ripple glass account.
The support email is at the contact us link.
If this is Jaron Theye,
I found a cancelled subscription in our ordering system.
It appears you signed up for a Premier subscription but never renewed it since January 2024.
I am surprised that you were able to even see the Premier plug-in.
You should only be performing Manual downloads from your account since SLP is not listed in the WP plug-in directory.
So yes, you can either purchase the Experience and Power plug-ins, or log into your account and renew your Premier annual subscription fee for $275. If you do not need any of the Premier features the add-ons would need to be purchased separately
Could you send an email to support with information regarding your account.
I cannot find your account via the name on this forum post so I am not able to check the status of your purchases regarding your Premier account .
You have not provided enough information to venture a guess. T
versions need , add-ons to the plug-in?
If you used the SLP SaaS I would be able to see the back end and your settings.
Without that I info I am at a loss how you have selected or activated various settings, radius etc.
Please provide Plug-in environment as indicated in our Read before posting guidelines.
Carolyn
Yes, I see you downloaded the free SLP base plug-in.
But I do not see anything in the support. You need to log into your account and use the current version of Power as well if you are using that or any other add-ons.
If you can provide the environment for the Plug-in it should also show the PHP. I looked at your site and it appeared you had 2301-14 version of base plug-in. We are now on 2503.20 But hold off updating until you send the debug log.
If you downloaded a newer version of Power it may not work with older versions of plug-in.
Hello Carolyn,
Can you email support with the debug log. The developer would like to look at it to narrow down the issues. Also what version of SLP and Power are you using?
The “vulnerability” is a non issue . Because of the chaos surrounding the WP and WP engine we have not been able to get them to respond.
We will be having another update before the end of this month if you want to wait.
You would have to download the plug-in and manually update , there is no auto updates of SLP plug-in through WordPress.
The version you are showing does not exist. When I visited your site it was showing a version of SLP from at least 6 years ago.
We do not have an add-on called pro.
I cannot recreate your issue. If you wish to update to a current version of the plug-in, Log into the SLP account in the versions and download the current SLP version. I do not know if it will be compatible with the rest of your plug-ins if you have not updated them as well. As far as not geocoding, you would have to look at your Google API key and make sure you have the right kind. They changed billing multiple times over the years and again on March 1.
Alternatively you can switch over to the SLP SaaS. Read in documentation the pros and cons.
P.S. If you update to newer versions , that may solve the issue. There will be another update coming end of Feb- march
I believe this was answered in the support email
I do not see any huge issues with that csv file, so not sure what to tell you. Make sure you are using the latest versions.
Double check that csv file for formatting.
https://wordpress.storelocatorplus.com/support/slp-versions/
P.S. I imported the CSV file that you attached into my SLP SaaS Staging site. (new release scheduled for the end of the month) and the import was slow but the entire file did import correctly, even the locations that had obvious errors (like Australia as a zip code with country US)
DeDatt,
lance is concentrating on updates to the SLP SaaS. I have no idea what version 2025.19.02 is. The ;last update to the WP plugin is version 23….
I am no longer testing , nor do I have access to those old versions.
We are suggesting customers move over to the SaaS.
Side note:
Because of the recent chaos in the WordPress environment over the WP Engine controversy and related funding issues, we’ve been having problems getting responses from WordPress.org. This is preventing our updates with Store Locator Plus® from being listed in the WordPress plugin directory. This ongoing lack of stability within the WordPress plugin directory has led us to make the decision to focus efforts on our SaaS offering. The SaaS offering provides our service on all web presence platforms, including WordPress.
P.S. If you go to the site reporting this you will see this ”
Solutions
This security issue has a low severity impact and is unlikely to be exploited.
This is not a vulnerability. The developer is aware of this as identified by the poster ,
when the locations in your dataset is marked private you can still find the url.
We do not see this as sensitive or a vulnerability considering the type of use the plug-in is intended for. Just delete any locations you don’t want to be shown instead of marking them as private.
Please list any other issues you have found or specific info reported if it turns out that’s not the “sensitive data” they are referring to.
The plug-in is not intend for sensitive data use. It is intended for the ability to find locations for your customers queries.
This is not a vulnerability. The developer is aware of this and identified , the “Private” marked locations in your dataset can be located through their URL. We do not see this as a vulnerability..
Do you have any locations in your dataset marked as private?
Solution:
Simply do not mark locations as private in your data set.
Please list any other issues you have found.
Could you share what sensitive data exposure was found as a vulnerability so I can pass it on to the plug-in developer? He is working on updates as time permits.