[Ernest Marcinko]

Hi!

I’m not sure about the first case, but the second should definitely work. In most cases wrong configuration is the cause, but it’s extremely hard to tell unless I see it.

There is a known bug with the current version, which affects a very small percentage of installations (database tables running onthe MyIsam engine). To make sure it’s not that, just open up the Fulltext search Settings submenu, and save the options without changing anything there. If there are no options to save on that page, just a message saying “Fulltext search not available ….”, then it’s definitely not that.

If you could provide temporary admin and ftp access to your staging or test environment would help a lot.

[Ernest Marcinko]

Hi!

I’m assuming you use multiple instances. Every search bar instance has a unique ID. The ID format is like this:

ajaxsearchpro{instance_ID}_{occurence_number}

As you can see there are 2 numbers, one identifiing the instance and the other tells how many times this search instance is placed on the same page.
So for example if the first instance is used once, then it’s ID is going to be this:

ajaxsearchpro1_1

If you use this instance again on the same page (the same shortcode twice), then it’s going to be:

ajaxsearchpro1_2

Same is true for the results and the settings container as well:

ajaxsearchprosettings1_1

and

ajaxsearchprores1_1

Now, if you want to target every occurence of the first instance, you can use this:

[code]
jQuery(function($) {
var text = ‘default text’;

$("div[id*=’ajaxsearchpro1_’] input.orig").val(text);
});
[/code]

To target only the first occurence of the first instance:

[code]
jQuery(function($) {
var text = ‘default text’;

$("#ajaxsearchpro1_1 input.orig").val(text);
});
[/code]

Same way you can target the settings container:

$(“div[id*=’ajaxsearchprosettings1_’] “) ….

or only the first occurence:

$(“#ajaxsearchprosettings1_1”) ….

Please note that these are advanced uses of jQuery and CSS. To understand how all this works you should definitely google “jQuery basics” and “CSS selectors” for more detailed explanation.

[Ernest Marcinko]

Hi!

Thank you for the details. I tried as you described, but I get everything correctly: http://i.imgur.com/OgHoRqt.png

I’ve also checked the ajax responses, everything is normal, no delays, no error messages. It might have been a minor server outage?

[Ernest Marcinko]

Please be much more descriptive with these issues.

Was the “visual broken” shortcode an issue before?
What do you exactly mean on visually broken? Is it a CSS problem?
Are you using the shortcode in a post? Are you using the shortcode in the theme?
Is the shortcode used in valid XHTML environment?
Is it happening if you turn off every plugin and switch the theme?
Is it happening if you turn off every plugin but not swap the theme?
Is your browser console showing any errors? Do you see any PHP error messages?
Is the error reporting turned on in the wp-config.php file?
Can you check for CSS conflicts in theme or plugin files via your browser inspector tools?
Do you have a visual screenshot of the problem?
What measures did you exactly do to solve the problem? I mean solutions listed in troubleshooting section of the documentation.

Sorry about the questions but it’s extremely hard to debug anything if I can’t see it.

[Ernest Marcinko]

Hi!

Is this happening with the old version or with the new I sent you?

It should be working that way, but I’m not experiencing this bug on any of my test servers nor on this production.

[Ernest Marcinko]

Hi!

Please read the first chapter of the documentation about safe update. It will most likely help you: Online documentation

• This reply was modified 10 years, 11 months ago by Ernest Marcinko.

[Ernest Marcinko]

Hi again!

1. “Higher but smaller” – smaller in which dimension? The items are smaller?
2. with a small CSS snippet:
[code]
.promagnifier {
display: none;
}
[/code]

3. This is a bit more complicated issue. I can see you are using custom CSS to keep the search open if the visitor hovers over the “#menu-search” element. This works fine with child elements.
The settings and the results elements are not siblings, children nor adjacent to the menu item, therefore it is not possible to target them with CSS. Another problem is that there is no delay to define in css, when the user hovers between 2 different elements. The only possible solution I can see here is some kind of custom javascript code.
Here is a basic solution, which might work:
[code]
<script>
var t;
$( "#menu-search, .vertical.ajaxsearchpro, .ajaxsearchpro.searchsettings" ).hover(
function() {
clearTimeout(t);
$(‘.ajaxsearchpro.asp_main_container’).css({
‘width’: ‘250px’
});
}, function() {
t = setTimeout(function(){
$(‘.ajaxsearchpro.asp_main_container’).css({
‘width’: ‘0’
});
}, 1500);
}
);
</script>
[/code]

However you will have to think through all possibilities and action and the expected turnout as well. This is just a very basic solution, it might get much more complicated.

4. I will make a blog post once it’s finalized.

[Ernest Marcinko]

Then it’s definitely something with the new update, will check on that soon.
Are you using isotopic layout by any chance? Is it happening on different layouts as well?

[Ernest Marcinko]

Localhost can easily explain that. I’ve seen issues with some wordpress core functions on localhost environments.
If you move to production and the problem persists, then contact me with login details and I’ll check for errors of course.

[Ernest Marcinko]

Hi!

1. To fix the settings box, use this:

[code]
div[id*=’ajaxsearchprosettings’] {
z-index: 999999 !important;
}
[/code]

2-3.
I have changed the ajax handler on the compatibility option of the plugin, and it seems to have fixed it temporary. You might need to clear your browser cache to see the change.

It’s hard to tell what can be affected, but you should definitely report this issue to the plugin author so he fixes it for the upcoming updates. You can try to use the

4. For more information about the shortcodes, please check these chapters from the documentation:

• Search shortcode in themes
• Search shortcodes explained

I have no idea where to put them to be honest. Every theme is very different in therms of code. The best option is to ask the theme author. They usually know the best which files and how you have to edit them.

[Ernest Marcinko]

Pleae update your ticket with proper temorary admin login and FTP details so I can check on these issues. There are no known causes, so it’s impossible to tell without even seeing it. I suspect some kind of plugin conflict, but I’m not sure.

You can add these details by editing your first post in this thread or by attaching a .txt file with them. Both methods are safe and only visible to me and you.

[Ernest Marcinko]

Hi!

I need more information on the “domain.com/undefined” issue.

• Since when is it happening? Have you changed any configuration regarding result URL?
• Is it happening on custom post types or regular posts or something else?
• Is it happening on every result, or only some of them?
• Do you have a working url where I can check this?
• Are you using any kind of filter function on the results?

The result URLs are parsed via the built-in get_permalink( $id, $leavename ) WP core function, so if this is returning an incorrect url, then this might be related to something else as well.

[Ernest Marcinko]

Hi!

My best guess is adding a min-width attribute to the input field. This issue is known for some cases, the upcoming update will have a different approach so this should not appear again.

In the meantime, I suggest the following CSS code:

[code]
input.orig {
min-width: 200px !important;
}
[/code]

“200px” usually works, but you might have to change that to a lower/higher value. You can add this custom CSS code to the Ajax Search Pro plugins Theme Options -> Custom CSS panel.

[Ernest Marcinko]

Is the post in that category? If so, then it is excluded.

The default behavior of category selectors is an “AND” logic – “don’t match any excluded”
You can change this to an “OR” on the General Options -> Behavior panel, which translates to “Match any of not-excluded”.

[Ernest Marcinko]

Hi!

There might be something else as well. I have tried a few bootstrap powered themes, but haven’t experienced issues.

My first suggestion would be to change the Javascript Source option on the Compatibility Settings submenu: http://i.imgur.com/sRJUDzZ.png
Try all the 4 options, one of them might work. On the same page there are 3 other options as well, which you can try to turn off: Load the polaroid gallery JS?, Load the isotope JS?, Load the NoUI slider JS?

If none of this works, then if you have an url where I can check the conflict, then I might be able to tell what’s exactly causing it.

[Author]

Posts