[Ernest Marcinko]

Hi!

That’s what I was going to say. There are 4 different sources availabe for the scripts. Two of them is namespaced (scoped). By default this namespaced version is in use.

Before jumping into changing the code, you should try out the non-namespaced versions first. It helped once someone wiht a similar issue, it wasn’t jquery UI but something else. I’m working on these javascript compatibility issues over 2 years now, and I honestly have no idea how a namespaced js can conflict with an entirely different one – it beats me.

Anyways, on the backend, go to the Compatibility Options menu under the ajax search pro menu bar. There should be a dropdown box with the JS source. Try the minified or the non-minified one. I have a feeling it will help.

[Ernest Marcinko]

Hi!

Could you please link me to the page where this is happening?
Could you please provide temporary admin/ftp access to check the configuration?
Also could you tell an example phrase to search for and the expected results?

The search speed mostly depends on the server speed and the configuration. If your database is big, it’s highly advised to disable search in categories/terms and content as these queries take time for the sql server and for many rows title is more than enough. Also the results count should be limited to around 10.

[Ernest Marcinko]

Side note:

I got a mail delivery status failure from your profile, so I looked and your mail address looked incorrect, it was **@monsooncommerc.com, I figured it missed an e from the end so I changed it to **@monsooncommerce.com

Hopefully you will get the support ticket notifications now.

[Ernest Marcinko]

Hi!

I just looked at the search main source. Is this happening on the post editor page?
Currently the built in UI is only loaded on the search backend pages and on the post editor.

However I’m not sure why I enabled it on the post editor, it might have been a mistake. If you open the plugins/ajax-search-pro/ajax-search-pro.php and go to line 85 where you should see this:

[code]require_once(ASP_PATH . "/backend/settings/types.inc.php");[/code]

then try to comment out that line, because I believe it’s not necessary to include that file there:

[code]//require_once(ASP_PATH . "/backend/settings/types.inc.php");[/code]

Try to refresh the page, and the UI and all the other js and stylesheet files should be gone on the editor page afterwards.
Let me know if this was indeed the issue, so I will add it to the bugfix list.

[Ernest Marcinko]

You don’t need any plugin requirement to run the search properly. And it runs properly on my side, that’s all what I’m trying to say.

If it runs correctly on my 3 different computers and on 5 different VPN proxy servers, then it should surely work on your side as well.

The problem is not related to this search plugin.

[Ernest Marcinko]

Ok then.

It definitely must be some kind of caching or something similar. I tried on 3 different computers, 3 browsers with each computer, on ipad, iphone and every of these displayed normally.

I also tried 5 different VPS providers with proxy via hola proxy plugin and it worked every single time. I refreshed like 100 times for each browser but it always works.

There must be some kind of caching bound to your IP address or your DNS points to a different IP address.

I’m 100% sure it would have showed up at least once in my test environment. I truly tried like 1000 times and everything is normal.

Try to flush your DNS cahce from the command line with the ipconfig -flushdns command, then try to restart. Also, check your hosts file if the site IP address is not overridden there.

[Ernest Marcinko]

Which version of the plugin are you using?
Which version of the internet explorer are you using?
Is the internet explorer compatibility mode disabled? It might be emulating IE8 or IE8 standards, it happenst with IE10 many times.

If you are using older plugin version 3.1, then there was an update regarding this issue which had been fixed. If you open up the wp-content/plugins/ajax-search-pro/includes/shortcodes.php file and go to line 22 you should see this:

[code]if(isset($_SERVER[‘HTTP_USER_AGENT’]) && preg_match(‘/(?i)msie [1-8]/’,$_SERVER[‘HTTP_USER_AGENT’]) ) {[/code]

If you see this exact line, then you should change it to:

[code]if(isset($_SERVER[‘HTTP_USER_AGENT’]) && preg_match(‘/(?i)msie [6-8]/’,$_SERVER[‘HTTP_USER_AGENT’]) ) {[/code]

This should fix the issue if you are using version 3.1

[Ernest Marcinko]

Hi!

1. No problem.

2. What screen size, resolution and browser are you using? It looks like the search is zoomed in in the browser on that picture, which can cause the webkit browsers to wrongfully display the backface of the animated object.

3. The fix is not yet done, the next version comes in 2 weeks.

[Ernest Marcinko]

Hi!

Sure thing. I’m not sure if it’s the same issue, but it might be. I’m attaching the zipped modified file to this reply. Let me know how it goes. In case something fails, just deactivate and delete the plugin in the plugin manager and reinstall it, your settings won’t be deleted.

I will remove the other topic, you can feel free to answer here. This is my last ticket for today, will answer tomorrow morning if the solution would not work.

[Ernest Marcinko]

Hi!

1. On the Layout Options -> Results behavior panel there is an option called “Sroll the window to the result list?”. If you turn it off, it won’t scroll to the result list.

2. Which resolutions exactly? I could not replicate this in my browser.

3. It’s a known minor issue, it’s addressed in the upcoming version.

[Ernest Marcinko]

Here is a screenshot of my IE10 of the page: http://i.imgur.com/93aFfnd.png
It looks just like the mozilla, it must have been the page cache only.

[Ernest Marcinko]

Was the first browser internet explorer 8? Because IE8 is not supported anymore, it loads the default search engine instead.

[Ernest Marcinko]

Hi!

It must have been your site cache.

This is how it looks on my computer: http://i.imgur.com/DllVrz4.png
This is how it looks on my iPad: http://i.imgur.com/GnqMPEP.png

[Ernest Marcinko]

Hi!

This sounds like a 3rd party javascript conflict coming from another plugin/theme. It’s extremely hard to tell which plugin might cause it unless I see it.

One of these should definitely help:

• Try to temporary disable all plugin but the search, and see if it works then
• If not, then try to temporary switch the theme to the default and see if it works then

Unfortunately many plugins tend to load all of their scripts without checking if the actual plugin page is active. Hopefully the suggestions above will help you.

[Ernest Marcinko]

Hi!

Could you please link me to a page where this issue is present? It’s probably a styling or a javascript problem. I might be able to tell if I see it live.

[Author]

Posts