[Ernest Marcinko]

Hi!

Thanks for the issue report, I was not aware of it, and it looks like the latest version is affected.

To fix it go to the Compatibility Settings submenu and change the Javascript source option to either “Minified” or “Minified scoped”. One of them should solve the problem.

I will check what is causing it and fix it for the next release.

[Ernest Marcinko]

Updating to the latest version, an then turning off the Crop Images for Caching option on the Compatibility settings submenu: http://i.imgur.com/zYMlXLu.png

[Ernest Marcinko]

The problem with your request is that you want to highlight the term on the actual single result page, not on the search results page, that’s a very big difference. I highly doubt any of these solutions will be helpful in this case.

There is a highlighter in the search included but it only works on the ajax results not on the actual results page.

One solution might be to pass an extra get parameter with the search results url. It is possible to change the result url wihtout changin the code using the proper filter, here is an example: https://wp-dreams.com/knowledge-base/how-to-change-the-results-url-to-something-else/
So like adding an extra parameter, something like:

$results[$k]->link .= “?highlight=” . $search_phrase;

But then again the $search_phrase variable is not defined, so you will have to somehow get it there, I don’t know how.

Then with another filter you will have to change the content or connect with the highlighter plugin somehow, because now the

$_GET[‘highlight’]

variable contains the highlightable phrase.

But then again, that’s just a suggestion from the top of my head. This is way beyond the plugin capabilities. I can give you suggestions or help, but I’m afraid I can’t solve this for you right now.

[Ernest Marcinko]

Well, if you are using the query caching or image caching then leave it of course.

If you have a high number of images I strongly recommend not deleting it, as it saves lots of performance. If most of those files as images that it means it saved extreme amounts of bandwidth, because it served these cached thumbnails instead of the full sized images.

If you however don’t want to use that cache, you can update to the latest version, which has a feature to disable the image cropping function and it won’t generate any thumbnails. The downside is of course, that the results will display the original sized images scaled down to the thumbnail size, which means much more bandwidth.

[Ernest Marcinko]

300 MB? How is that even possible?

The plugin does not have this size, the installer is 1.8 MB only.

Maybe you had search phrase caching activated and the generated files grow this size? Can you check which folder contains the most of the data?

[Ernest Marcinko]

I’m not sure if it’s doable, but this is what you can try:

1. Decrease the Minimal character count to trigger search option to 0 on the General Options -> Behavior panel
2. Turn on the Trigger search when changing a facet on settings? option on the same panel.

The only difference, that the categories can only be displayed in checkboxes. Other display types like radio, select box etc.. is coming in version 5.0. (or maybe sooner if I can finish)

A select drop-down can only be created on values in custom fields. For more info you can check the documentation chapter or the custom field filter video guide on this.

[Ernest Marcinko]

It’s a difference in configuration of image cropping as far as I can tell. On the production the “Crop images for caching” option is turned ON on the Caching options panel, and on the staging is turned off. It basically saves a bit of server performance when turned off.

Can you give one or more example queries that I can try on the production, that returns results from both languages?

[Ernest Marcinko]

How about increasing the width values and perhaps adding media queries for different browsers?

First, try setting the fieldset width to 100%:

[code].searchsettings fieldset {
width: 100% !important;
}[/code]

then the options to a min-width of 200px and a width of 45%:

[code].asp_option_cat {
min-width: 200px;
display: inline-block;
width: 45%;
}
[/code]

Try different values as well, but this way the width is going to be 45% on bigger screens, and minimum of 200 if it goes down. And if the screen is too small it automatically breaks the line to 1 column.

The space on C2.jpg is because of the line alignment. Since the first element label is broken to two lines because of the 200px width, it icreases the line height, and the second one is printed to the line bottom by default. You can try increasing the line height or the vertical alignment, but as I can see there are more animated elements on the page, including the scrolling, and different vertical alignments may cause blurring in the text (browser bug). There is a good chance you will have to live with it, I don’t see other solution in inline-block mode.

[Ernest Marcinko]

Make sure you clear your site page cache for the changes to apply.

In case that does not work, then can you please provide temporary admin and FTP access to check on the issue? I’m not able to replicate it on my test servers. You can add access by editing your first post in this thread, or by uploading a .txt file with the details. Both methods are safe.

[Ernest Marcinko]

But the screenshot you attached shows the Keyword suggestions panel and not the autocomplete, those are 2 different things.

If you siwtch to the Autocomplete panel, the google should be still there.

[Ernest Marcinko]

“But the feature doesnt seem to work properly.”

Can you please explain the problem in more details?

[Ernest Marcinko]

Well, then there might be a different problem as well.

The regular engine joins the WPML translation tables with the posts tables, and filters the elements withe the correct translation code only. It might mean that there is some kind of mix-up with the translation codes or IDs.

I have no option but to study the WPML source and see what it does to new items, and missing translation IDs. I will probably make a few changes to the staging code that you can try on the production environment.

Will let you know when I have changed anything.

[Ernest Marcinko]

Hi!

It’s the search autocomplete function and you can turn it off entirely on the Autocomplete & Suggestions -> Autocomplete options panel: https://i.imgur.com/aSrvXKQ.png

For more information, you can read the chapter related in the documentation: https://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/autoc_keyword/autocomplete.html

[Ernest Marcinko]

That’s right, it should work, they must be identical.

You still got results in both languages or is it something else?

Does it work if you switch to the “Regular engine” instead of the “index table engine” on the search options panel?

I may have 1 more trick to try, but I honestly have no clue at this point what exactly is wrong. I feel like there are missing translation ID’s are causing the mystery, as I can’t think of any other possibility here.

[Ernest Marcinko]

Hi!

I’m afraid it’s not possible. If you want, I can add this as a feature request for a future version, but I cannot promise anything, as I’m not sure if it’s actually doable.

[Author]

Posts