[Plugin: Google Maps via Store Locator Plus] Search function not working

UPDATE:
So I tried systematically changing settings and I got the map to function by deselecting “Force Load JavaScript:” on the Map Settings page. I would say that is a bad thing to have checked by default!
__________________________________________________________

Original:

Greetings, after updating the Store Locator Plugin to the latest version, it is no longer functional. Using the Firefox Error Console, I’m getting:

doing search@(37.86373760000001, -122.26822449999997) for radius of 50
csl.js?ver=3.4.2 (line 967)
searching: 37.86373760000001,-122.26822449999997
csl.js?ver=3.4.2 (line 967)
jQuery(“#searchForm”).formParams is not a function
[Break On This Error]

var formObj = jQuery(‘#searchForm’).formParams();

csl.js?ver=3.4.2 (line 1030)

Any ideas?

So I tried systematically changing settings and I got the map to function by deselecting “Force Load JavaScript:” on the Map Settings page. I would say that is a bad thing to have checked by default!

@nhtqhoe – it needs to be on by default because 30% of the themes out there do not properly support WordPress 3.3+ footer processing. If they are not updated correctly to support those function calls the maps never work on those themes.

It is smarter, better, and generally a faster way to do things with Force turned off, BUT more sites break with it turned off than the other way around.

Also, it should not break in EITHER mode unless something is messing with the JavaScript stack very early on. Themes and plugins that do not use proper register and enqueue methods seems to cause all sorts of issues.

Any update on possible patch/fix for the problem I am having? Thanks!

@MyChiroPactice –

The patch is out tonight, 3.6.2 works around the ThemeForest bug. I will write a blog post about what is broken and why. It is definitely a ThemeForest issue, they are not using wptexturize() properly.

It broke because 3.6 HTML was tweaked to make it easier to read, support, and less prone to bugs. The HTML was written with extra white space on the table definition so I can easily see the attributes. It is standard practice and is an accepted “best practice” when writing complex HTML documents.

ThemeForest decided to replace the HTML newlines with
which is WRONG. HTML should never be “texturized”. In addition the WordPress wptexturize() function should honor the shortcode ignore list, but the custom ThemeForest “wptreats_formatter()” ignores the ignore list.

Short version, yeah, I changed some HTML coding by adding extra whitespace in 3.6. That should NOT break anything. ThemeForest has a bug that made it look like SLP was broken. SLP, I hope, now works around their bug with this release.

Learn more about the open HTML, ThemeForest, and the SLP patch:
https://www.charlestonsw.com/themeforest-and-texturizing-shortcodes/

Great! Thanks for the quick patch – truly appreciated.

Hi. I updated the plugin but the same pesky issues persist. Any idea why it’s doing that? Thanks and sorry to bug you about it.

@mychiropractice

If you are seeing open HTML under the map I can say for certain, after spending a lot of time tracking the issue, that the problem is a theme or plugin mis-handling shortcode HTML output.

If you are using a ThemeForest theme you may want to consider something different. I just created a post explaining my reasoning, but I will be providing very limited support for Envato based themes given their obvious lack of desire in helping sort out any conflicts with their themes.

I’ve already spend a combined total of 8 hours while on vacation trying to create a hot fix for something that turns out to be a bug in a core Theme Forest function. If they put ANY effort into fixing their own issues or working with me to come up with a solution I’d consider working further on a solution. However, spending hours on code patches to work around bugs in other products is not a productive use of my time.

If you really need to use a Theme Forest theme and are still having issues I can provide custom support and debugging for the standard support fees posted on my website at https://www.charlestonsw.com/support/.

Hi Lance,

Your time and efforts are certainly appreciated, and if it takes a few hours of your custom development time to get it done, then we have to move in that direction.

My only questions is that the plugin was working just fine with the Evato theme since May, and it is only in the past two weeks that this issue has come up.

Regardless, the theme is something that has been heavily customized to fill the need of the client, so we have to think of patching it up.

Whats the next step for support, and what timeline can I expect for a fix?

Google Maps via Store Locator Plus – After upgrading search not working for me..

Please any one help me…..

Link:- https://fabricosundomes.com/dealer-search/

Thanqs in advance

@mychiropractice – If you read the article on my site it explains in detail why the plugin “suddenly broke” with the Envato theme you had in place for months. I added some whitespace to my HTML code to make it easier to read & maintain. There is a bug in Envato’s wptreats_formatter() function that incorrectly bastardizes valid HTML syntax by inserting HTML break tags in the MIDDLE of other HTML syntax.

As for support, you need to purchase it from the website and I will put it on the schedule. Since I am just returning from vacation I have a few days of coding to take care of but will take a look as soon as I can, likely not until Monday but possibly before.

@lakimathan – please start a new thread if this is not related directly to the open HTML issue.

@lakimathan – looks like something your version of jQuery does not support the form processing script that was added. I will see what I can find, but please start a new thread.

@mychiropractice – If you are still having issues with your ThemeForest theme, please post the name of the theme here. I have a contact at Envato that will help work with the author of the theme to get the issue resolved.