[Ernest Marcinko]

Hi!

I see you solved the word match problem. I believe you had the “AND with exact keyword matches” keyword logic selected on the General Options -> Behavior panel.

As for the croatian translation for the “Search breed…” text I recommend this very simple solution:

1. Make a duplicate of the search instance: http://i.imgur.com/FYyO2Fj.png
2. Edit the “Search breed…” and any other text in this new search instance to croatian.
3. Use this new search shortcode in the croatian version of the article 😉

[Ernest Marcinko]

Hi!

Please check/try the safe update steps as described in the knowledge base or in the documentation.

[Ernest Marcinko]

Hi!

Please check if you didn’t enable AAPL support by accident. General Options -> AAPL options tab. Everything should be disabled there: http://i.imgur.com/Rfztmdx.png

This happened before, so that’s my blind guess.

[Ernest Marcinko]

Hey!

I believe I have already uploaded a fix regarding this to codecanyon. If you have downloaded the search before 9th of april, then could you please re-download and re-install the plugin? I think that will solve the problem.
Just deactivate and delete the current version then upload and activate the one you download. Your settings and search instances won’t be deleted. Let me know if the issue still remains!

[Ernest Marcinko]

Hi!

Could you please be more descriptive?
What type of content are you searching? Posts, pages, custom post types, terms..?
Which fields are concerned? Title, content, excerpt, custom fields?

Can you provide an url to a test or staging environment and backend + ftp details so I can run tests regarding the problem?

Can you also provide examples of the problem? (which keywords should return which results, etc..)

If the fulltext is not available, it’s a good sign – since keyword logic is won’t work in fulltext search mode. It’s all right if fulltext is not available, it’s not required at all. Most database hosts are not using it anymore.

[Ernest Marcinko]

Hi Adam!

Luckily, that icon is not used on the site, since the settings icon is not visible. The png icons are deprecated, only a few search templates have them – others use SVG icons. This must be something I’ve missed, apologies for that.

I’ve logged in with the credentials you gave and changed the settings icon to another one. This won’t change anything visually, but a new CSS file is generated, now without the sett0.png icon reference.

Once you clear your CDN and page cache, the search stylesheet should no longer contain this icon, and the pagespeed should not report it anymore 😉

[Ernest Marcinko]

Sure.

So I figured out that the breeds are stored as product tags. And that’s the solution, you need to search product tags instead of products.

I’ve turned off the search in posts and pages and products and on the General Options -> Sources 2 panel I dragged the product tags as the source: http://i.imgur.com/ftIg5KY.png

Now I’m getting results like this: http://i.imgur.com/gPyX92M.png

I hope that’s what you were looking for.

[Ernest Marcinko]

Hi!

In case you are using the isotopic layout, I would suggest to try 50% width for the items.
Try to force it with this CSS code:

[code].rpp_item {
width: 50% !important;
}[/code]

I’ve tried this, and it looks like it works, at least on my test environment.
Full width window size: http://i.imgur.com/j6Owfph.png
Smaller window size: http://i.imgur.com/GItN4ie.png

I’m not sure how this would work on more elements, it might not.

Since there is a margin and padding as well on the box, the items may appear as non full width, but I figured out an elegant way to make the container appear without padding like this: http://i.imgur.com/8gMvOMT.png

Go to the Theme Options -> Container Layout panel. Then set a negative margin on the left and right of the box. In my case it was -10px, but you might have to experiment. Also, set 0px for the left and right padding of the box. Here is how I have it: http://i.imgur.com/2Gb72V7.png

That should stretch the container to width where the items appear to occupy the whole width of the post.

[Ernest Marcinko]

Hi!

There are many factors that can influence the search speed:

• Database size
• Too many (usually over 8) or poorly programmed plugins
• Server speed

You can learn more about these here: http://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/performance_tuning.html

There are a few ways to fine-tune the search: http://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/performance/fine_tuning_the_search_configuration.html

Plus there is a known issue with WooCommerce (if you are using it). They did something in version 2.3 whereas every plugin that is using ajax is slowed down significantly (about 2-3 more seconds). It’s been confirmed by many other plugin developers as well.
We and other developers have already contacted them, but they are refusing to answer or help. Hopefully one of them will respond eventually.

[Ernest Marcinko]

Hi!

I’ve tried the link you provided, but instead of the page, it gives me a file download for some reason. I tried with firefox, chrome and IE11, but none of them seems to work.

For WPML there is nothing extra to add, the search should display the results in the correct language by default. I might have made some changes in your case, I can’t remember, it was a week ago I think.

If you can re-enable my access I can check.

[Ernest Marcinko]

Hi!

I’ve made a few changes to your setup, and I will explain why.

1. You had Caching (Caching options) and Custom ajax handler activated (Compatibility options). The problem with these is that caching is not yet WPML ready, and the custom ajax handler only loads the most neccessary plugin events – and WPML loading is not registered as one. This resulted in passing the wrong language code to the search, so I had to turn these options off.

2. The Advanced Ajax Page loader options were enabled. I’ve turned them off, now it should work as expected.

3. and 4. You have to exclude the categories on the Advanced Options panel. (you will see if you scroll down). The Frontend search options are only for appearance. I see you excluded a few categories on the General Options -> Sources panel, but that options is related to something else (when categories are results).

[Ernest Marcinko]

Everything is passed back to the includes/search/search_content.class.php file, that’s where the query is created.

Then, if you var_dump the $res variable in the hooks.php file, you will see which results you get.

Also, I use to dump the query as well to check for errors and such, line 595 in includes/search/search_content.class.php. The line is already there, you only need to uncomment.

The almost final query is on lines 348-382. Parts within { } brackets are later replaced (like {like_query} and such).
The results are then post-processed, but this is the main query for both ajax and non-ajax searches.

[Ernest Marcinko]

Hi!

1. This is unfortunately not possible.

2. Could you please explain what do you mean by no “real” drop down?

3. Only by adding a few lines of custom CSS and altering the code.
Add this custom CSS to make the slider elements invisible:
[code]
.searchsettings .asp_noui_lu {
display: none !important;
}

.searchsettings .noUi-target {
display: none !important;
}

.asp_custom_f input[type=text] {
width: 30%;
}
[/code]

Then open up the plugins/ajax-search-pro/includes/views/asp.shortcode.custom_fields.php file and go to lines 94-95, where the beginning of those lines are:

[code]
<input type="hidden" …
<input type="hidden" …
[/code]

Change the input type to text on beginning of those lines, like this:

[code]
<input type="text" …
<input type="text" …
[/code]

Save the file. Then you should see text fields instead of the range slider.

[Ernest Marcinko]

Hi!

I believe you will have to exclude all the other product categories, and leave only the “Mačka” and it’s subcategories.

More information on how to do that: http://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/advanced/excluding_categories_&_terms.html

Also, make sure that the “product” custom post type is selected for searching: http://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/general_settings/search_in_custom_post_types.html

[Ernest Marcinko]

http://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/general_settings.html

[Author]

Posts