Lance Cleveland

This is fixed in SLP 4.6.2

WordPress changed version 4.6 to deprecate wp_get_sites() which returned an array.

They now require get_sites() which returns an object.

Thanks to these changes in WordPress, Store Locator Plus now needs to carry around a lot of extra code to basically say “If you are on Multisite and are using WP 4.6 do this… if you are on on Multisite and less than WP 4.6 do that… and if you are NOT on multisite do something completely different”.

As an aside, most of the multisite support options are built into the Premier Plugin for Premier Subscription users. If you are running multisite you really should be enrolled in our Premier program.

Your review should be limited to the FREE plugin that is offered here on the WordPress Plugin Directory, NOT the premium add ons nor the extended support services.

That aside, your claim of “forces you to pay additional monies” is absolutely false. All add ons release since version 4.2 of Store Locator Plus, which is over 2 years old, are still functional with the latest 4.6 release of the base plugin. You may need to login to your account at StoreLocatorPlus.com to download the latest version , but it is not disabled NOR do we ever require that you re-purchase the SAME add on you originally bought. In addition, the add ons will always continue to work with the version of Store Locator Plus that they were originally released with. Don’t want to go through the add on upgrade process? Don’t upgrade the base plugin to the latest release. You also want to be careful not to upgrade WordPress as they have been making significant changes lately that break a LOT of things in the plugin and theme world.

Eventually there MAY be a version of the base Store Locator Plus plugin that does not work with an add on from 3+ years ago. This is no different than any other software you purchase. WordPress 4.6 broke hundreds of plugins and themes that were multisite-aware. I’ve had to purchase the latest version of several premium plugins I use on my sites because WordPress changed something. I needed to get the newest version of those plugins *IF* I wanted to use WordPress 4.6 instead of version 4.4. (I’m still trying to get WP Ninjas to fix the premium Ninja Demo plugin I purchased – yes, THE WP Ninjas. Paid plugin, support that takes over a week to get answers, updates that don’t work… maybe I should write a scathing review on their free plugin here.)

Speaking of WordPress 4.4, that broke thousands of plugins and themes when they replaced the version of jQuery with a newer 1.12 release. Many of our clients had to purchase newer versions of their themes and plugins (but NOT Store Locator Plus) because they upgraded WordPress 4.3 to 4.4 and the plugins needed a new version installed to be compatible. Several sites had to find completely new plugins because the authors of the FREE plugin decided “I’m done earning nothing and having customers demand I fix this thing FOR FREE because WordPress changed something”. In the non-WordPress world we see the same thing but with a much steeper price. I upgraded my other laptop to Windows 8.1 and the thousands-of-dollars in Windows software that I had used for years no longer worked. Microsoft wanted me to now pay a monthly fee to use software that I paid thousands for just 4 years ago.

As an aside – when WordPress 4.5 came out we had 37 complaints that our plugin broke when they clicked updated. When we got on to those 37 client sites, 36 of the 37 issues were because ANOTHER PLUGIN broke. What 37 of 37 customers failed to mention was that they upgraded WordPress AND our plugin AND 10 other plugins AND their theme.

As far as your car analogy, it is very much flawed. What you are doing is getting a car FOR FREE then spending $50 on a high performance kit for the engine. 3 months later you go back and get ANOTHER NEWER CAR FOR FREE and get mad because your high performance kit for the previous car didn’t just bolt right on and work flawlessly. Funny thing is that unless your performance kit is more than a few years old we’ll even give you a newer version of that for free.

As for the quality of free support, we receive far more compliments than complaints. Sometimes my support staff can be less-than-friendly, I agree; though reading how rude and obnoxious some people can be I can see how they can be in a bad mood some days.

I’m a bit shocked by the claim everything breaks EVERY TIME you updated over the past 4 years. There are nearly 20,000 sites running Store Locator Plus at this very moment. Over 10,000 sites have upgraded to the latest release. Over 6,000 sites have upgraded at least FOUR TIMES in the past twelve months. Less than 100 issues have been reported about problems caused by an update.

Is the plugin flawless? Far from it, but it certainly is not completely broken on EVERY UPDATE for the past 4 years. If it was that broken we’d be getting 10,000+ complaints not a half-dozen. On a related note, there is an issue in 4.6.1 that we learned of just this week. The patch is coming out in 4.6.2 later today. Sites running WordPress < 4.4 or that are on WordPress 4.6 running multisite without a proper multisite license may run into a “function not found” error that will break the site. The fix? Stay on SLP 4.6 or wait for the 4.6.2 patch to come out in the next 24-48 hours to resolve the issue.

Sorry – they are both in Experience / Results… “Number To Show Initially” and “Max Search Results” settings. They should never be blank or you get “all locations”.

What is your site URL? Also – please register and post in the forums at https://www.storelocatorplus.com/ as the forum posts come up in our Slack and support channels so we know you need help. We don’t check here very often.

As for the limit – it should be applied on both a page load and search based on your settings under the Experience / Search (user search) and Experience / Results (initial page load) tabs.

This should be OK in the 4.4.37 release.

The CSS from SLP should only appear in the SLP tabs and Store Taxonomy (categories) page. Are you seeing it render on non-SLP pages?

@gusthefish – your notes about my support people asking you to pay $250 to get it to work is a false representation of the facts. CiCi misunderstood what you were asking for as she noted in that thread. She thought you were looking to deal with Google’s autozoom NOT the zoom tweak setting. She told you as much in your thread and indicated that the Experience add-on or Enhance Search add-on would not be necessary. She even asked you to update SLP to see if it would fix the issue. When it did not she understood brought the issue to my attention and followed up saying that the zoom tweak feature was being addressed.

In addition you have another thread open on the topic and CAN continue to discuss and follow up on the issue. Your rating here makes it sound like we are trying to rip you off by charging money for something to address an issue you brought to our attention. That is ABSOLUTELY not the case.

Related to the issue at hand , I posted an article today as to why zoom tweaking was adjusting by one zoom level based on the prior releases of the Google Maps API. There is an update to SLP coming this week with a patch to allow the zoom tweak to work as intended with the newer Google API.

Hey @ cici and @destanylaval – no direct email to me either and there is not record of an issue in the [email protected] email system or [email protected] email system, both of which are monitored and answered daily.

Giving a one-star review for a PREMIUM product which is NOT what this WordPress directory is for and basing that review on the fact that there was not personal 1:1 support within a couple of hours is bunk, IMO.

There are over 5,000 people using the Pro Pack and adding/deleting locations without problems. There are over 15,000 sites running Store Locator Plus live right this very moment. If deleting a location was an issue we’d have heard about it a thousand-times-over by now.

If there is a problem I’d love to know about it so I can chase it down and fix it quickly. Leaving a 1-star review is NOT the way to get things like this addressed.

@cobblehilldigital –

I cannot reproduce this on my WooCommerce sites (dev or our live site for SLP).

Can you edit base_class.ajax.php on your server in the store-locator-le/include/ directory?

If so, try adding these first 4 lines to the initialize function of SLP 4.4.10:

function initialize() {
if ( ! isset( $_REQUEST[‘action’] ) ) {
$this->short_action = ”;
return;
}
$this->short_action = str_replace(‘csl_ajax_’,”, $_REQUEST[‘action’] );
$this->do_ajax_startup();
}

Let me know if that helps so I can put it into the next production release.

Thank you @usmcveteran. Let us know if there is anything we can do to make the experience even better for you and your members.

Thanks @stilfx!

Thanks @spielerinternet!

Popup info box is being fixed in 4.3.04 coming next week.

The prerelease it out now (you can get it free at StoreLocatorPlus.com) but it has not been fully tested yet.

Awesome review! Thanks Brandon!

Fixed in 4.2.60.