[thesearchpro]

Hello, I setup your plugin and am now getting this JS error.

I searched the FAQ but could not find anything that addresses this error

Here is a screenshot: https://www.dropbox.com/s/gygsbu9ez2qbn8j/Screenshot%202017-05-06%2023.09.25.png?dl=0

[Ernest Marcinko]

Hi!

Unfortunately these errors are very uncommon, and impossible to debug without actually seeing it. The problem is coming from the initialization process, which tries to de-code the search parameters on page load. I’ve maybe seen a similar error about 1 or 2 times before, and it was related to a 3rd party script tempering with the HTML dom nodes within the search bar.

My first suggestion would be to delete the current search instance, and make a new one, to see if the problem persists. First, try it with the default configuration, to see if it works that way. If yes, then it’s almost definitely related to something else as well. If it’s resolved, then it might be a yet unknown issue – maybe with character encodings or something similar.

Let me know how it goes.

[thesearchpro]

I debugged the issue last night, you’re plugin is not escaping inputs for the “no results” message.

I used a “don’t” and the apostrophe broke everything apparently.

[Ernest Marcinko]

Thank you for reporting back.

The weird thing is, that it does actually. I recall this being an issue a few releases back, but I’ve added a function to filter all texts through the stripslashes() php function. That should do the trick, but I’m not sure anymore. I’ve tried to re-create the issue, but I’m able to input all kinds of text there, including special characters.

May I ask, if you use qTranslate, Polylang or WPML by any chance?

[Author]

Posts