[Ernest Marcinko]

Hi!

It’s working for me. I logged in, temporary deactivated the Yith WooCommerce Compare plugin, tried the search, and the results were visible. Maybe it’s your browser cache.

[Ernest Marcinko]

Hi!

Yes, it was a z-index issue.

Try to use the following custom CSS:

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

[Ernest Marcinko]

Hi!

Thanks. I just checked the ajax response, but there it’s halted with the following error:

Fatal error: Call to undefined method YITH_Woocompare_Admin::list_products_html() in /home/handlef/public_html/wp-content/plugins/yith-woocommerce-compare/widgets/class.yith-woocompare-widget.php on line 41

It looks like it’s coming from the “yith-woocommerce-compare” plugin. It triggers a fatal error, which causes the ajax request to fail. There is a good chance that every other ajax request is halted with the same error, it’s no good.
Please contact the plugin developer with this issue. In the meantime try to de-activate that plugin.

[Ernest Marcinko]

Hi!

I can’t see the search anywhere on your site. Could you please send an url where it’s visible?

[Ernest Marcinko]

Hi!

a. A category is unchecked if it’s excluded on the Advanced options panel. It’s the best case use, since you can give the user the option to include the posts from a certain category, even if it’s excluded.

b. Going to happen eventually, perhaps in the next update. Checkboxes and dropdowns work very differently on server perspective, and the current state of code is made exclusively on check-box versions.

c. I’m not sure about this.

Grouping to dropdowns based on parent categories – I’m not sure if this is going to be a feature, because of taxonomies. To define a group, wordpress offers using taxonomies, which is well supported core feature. In your case “Year”, “Genre” should be the taxonomies containing the terms (categories).

[Ernest Marcinko]

Hi!

It looks like something is catching the focus event (I’m guessing the slider) and prevents the default behavior. It’s extremely hard to tell what code is exactly causing it. I see dozens of new properties on each search element, I’m guessing it’s the slider doing it.

I think I might have a solution though without touching the slider. Try to add this custom javascript code to the footer of your site before the closing body tag:

[code]
<script>
jQuery(‘input.orig’).click(function(e){
jQuery(this).focus();
});
</script>
[/code]

[Ernest Marcinko]

Hi!

There are several ways to do that. I would not recommend editing the php code, as an update will ruin your changes.

I would rather recommend a javascript solution, which you can add to your site footer between script tags:

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

$(‘input.orig’).val(text);
});
[/code]

Just change the text variable to whatever you need to 🙂

[Ernest Marcinko]

I just disabled 3 lines in wp-content\plugins\related-posts-pro\js\nomin\type.wrapper.js, 154-156. The cause is yet unknown, this is the only solution that works for now.

For the upcoming update I will of course figure out a different way of solving this.

[Ernest Marcinko]

I’ve made the correction, it should be working now. I’ve tested with IE, it does not crash anymore here.

[Ernest Marcinko]

Sorry, it took me a while to figure out why this was happening, I was able to re-create it on my test environment.

Looks like one of the external scripts is causing the problem. Let me log in via the FTP details and try to fix it.

[Ernest Marcinko]

Hi!

I think you are looking for a different search keyword logic.

Please take a look at these chapters in the documentation:

• How to change the Search keyword Logic
• Keyword logics explained

I think your are looking to set the “Keyword logic” setting ti AND, as it will match only if both words matching each field.

[Ernest Marcinko]

Hi!

Indeed there is an issue. I’m going to fix it with the release of version 4.1.
It’s going to be very soon. In 2 days.

[Ernest Marcinko]

Hi!

Thank you for the kind words!

Sorry for the late answer, I’ve been working a bit too much on the upcoming version release and go too many tickets/mails as well with bugs and issues.

1. If I remember correctly there is a scrollbar issue related with the current version and I think in this thread I solved it, but I think I had to make changes in the code as well.

I can only fix this via FTP, but I don’t want to ask for access unless necessary. I have a better idea/solution. I’m attaching a pre-alpha version of the upcoming 4.1 to this post, which already has this issue fixed.
All you need to do is deactivate and delete the current and install this one.
Some features are not completely finished or tested, so you if you experience issues, just re-install the old version.

Also, you can try to increase the “Results box viewport (in item numbers)” option on the Theme Options -> Vertical Results panel if you still experience this problem after upgrading.

If you rather not update, let me know and we proceed from there.

2. There is no such class. This is a bit complicated issue, I don’t want to get into every exact detail, but it’s not possible. Mainly because there is no standard way for developers to “output” the default search, and everyone is using a different way. The result is that there is no one standard solution that works with each and every theme. Most of the modern themes are using completely different method outputting the search form making it impossible to replace.

The only way is to replace the source code directly with the search php shortcode. In your case, maybe something like this should work:

[code]
<div id="menu-search">
<?php echo do_shortcode(‘[wpdreams_ajaxsearchpro id=1]‘); ?>
</div>
[/code]

As your requests:

1. That is a good idea. Added to the future features list.
2. Yes, I’m going to re-work the grouping section to a better one. In the meantime you can use the editable template files, they were introduced in version 4.0. With these template files you are able to directly change the HTML output of results and groups.
In your case if you open the plugins/ajax-search-pro/includes/views/results/group-header.php file, there will be a bunch of comments for explanation and a single line of code:

[code]
<div class="asp_group_header"><?php echo $group_name; ?></div>
[/code]

If you change that to:

[code]
<div class="asp_group_header"><?php echo $group_name; ?> Articles</div>
[/code]

then the “Articles” string is going to be displayed after the group name.

3. Also a good idea. I’m adding this to the future features TODO list. There is a good chance I’m implementing this as well.

Let me know if you have any questions.

[Ernest Marcinko]

Hi!

Could you please provide a site url where I can check this issue? I don’t know if you provided temporary access, but on my end the fields are empty. You can upload a .txt file with the details as well, it’s safe, not visible to anyone else.

Sounds like some kind of error halts the ajax response – it might be coming from another plugin, or an unknown bug can cause it as well. If you can provide an url, I might be able to tell.

[Ernest Marcinko]

Hi!

Good news! I’ve managed to put together a (hopefully) working copy of the partially ready upcoming version.
I’ve implemented a way to display categories hierarchically. For now it looks like this: http://i.imgur.com/apreacq.png

It respects category exclusions, as well us multi-level hierarchy. I’m going to add a few options like level-margin, parent-child exclusions and do some more tests to verify every possible use case.

For now, I’m attaching this version to this post. Before installing:

0. (optional, but recommended) – make a copy of your whole site including database. Just to make sure everything is all right.
1. Please make a copy of the current search plugin files, which is located in the wp-content/plugins/ajax-search-pro folder
2. Deactivate & delete the current plugin version via. the plugin manager
3. Download & install the attached one
4. If something doesn’t work try the safe update steps: http://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/
5. If still doesn’t work, then let me know if there are any error messages or logs.

I’m hoping it’s going to work though.

[Author]

Posts