[Ernest Marcinko]

Try to add this css rule to the site css, it should solve this permanently:

.searchsettings .option label:after {
    border: 3px solid rgb(255, 255, 255) !important;
}

[Ernest Marcinko]

Hi!

I get results for “michale jackson the girl is mine”, but it takes very long, about a minute to get the results. It’s because of the big size of the database and the number of keywords. Because the “Show exact matches only?” are turned off, the search checks every word separately, and the more keywords, the longer the search. For 2 words it’s only a few seconds, but for 3,4,5… it’s much longer.

You can turn back on the “Show exact matches only?”, it will probably solve this, however then it wont work for different direction (michael jackson, jackson michael), but probably this is the only way to solve this.

[Ernest Marcinko]

Sorry, I sent my previous message with my test account accidentally 🙂

[Ernest Marcinko]

Hi!

No, you dont need relevancy for that.

[Ernest Marcinko]

Hi!

That is because those are product categories, which is a custom taxonomy. If you want to turn them off, you need to turn off the “Show the taxonomy selectors?” options on the same page.
They weren’t clickable, because there was something wrong with the “tick” color. If it ever disappears in the future, just change the “Settings drop-down tick color” on the Theme options->Settigns icon&Dropdown page and save the settings.

[Ernest Marcinko]

Hi!

No problem at all. I think it’s caused by a browser styling attribute, but I think it’s possible to turn it off. Try to add these lines to the site’s main css file:

input {
    -webkit-appearance: none !important;
    border-radius: 0 !important;
}

Here is an article about it: http://stackoverflow.com/questions/2918707/turn-off-iphone-safari-input-element-rounding

Unfortunately I’m not available for a custom job, sorry 🙂 I wish I had more time.

[Ernest Marcinko]

Hi!

The styling of the outlining div needed to be reduced from 360 px to 310 px in the template header.php file, now it fits.
I also added a few lines after the wp_head() call, to make sure, that the window.resize event is called after the user clicks the search icon, so the text input of the ajax search fixes itself:

  <script>
    aspjQuery(document).ready(function(){
       aspjQuery('#NavSearchLink').click(function(){
           aspjQuery(window).resize();
       });
    });
  </script>

Please backup the header.php file from your template in case you need to reinstall it, so the changes persist 🙂

[Ernest Marcinko]

Hi Sergio!

I’m guessing you are searching post comments 🙂 It’s only possible to change by modifiing the source code, but you only need to edit 1 line.

If you have ftp access, then open up this file: wp-content/plugins/ajax-search-pro/includes/search_comments.class.php and go to line 70, you should see this:

$commentsresults[$k]->title = substr($commentsresults[$k]->content, 0, 15)."...";

If you want to change it to 20 characters, then replace that line with this:

$commentsresults[$k]->title = substr($commentsresults[$k]->content, 0, 20)."...";

Let me know if it helped or you need any assistance with this!

[Ernest Marcinko]

Hi!

I’m not sure if by the time you have managed to solve the issue, but it looks ok now on my side. Sorry I couldn’t get to you sooner, I had 2 more tickets on hold 🙂

Let me know!

[Ernest Marcinko]

Hi!

I’ve managed to solve the issue, but I needed to edit the search code in many ways. I’m attaching a copy of the modified search in case you need to reinstall it anytime.

[Ernest Marcinko]

Hi!

I have already replied to your other ticket. I will install a new version tomorrow, that I have worked on today 🙂

[Ernest Marcinko]

Hi!

Didn’t forgot you. Today I was working on a fulltext version of the search, I will upload it to your server tomorrow 🙂 Hopefully it will fix that as well.

[Ernest Marcinko]

Hi!

It turns out it was a database error, somehow the necessary search tables weren’t created. I managed to alter the sql syntax with the db-manager plugin, now it should work fine 🙂

[Ernest Marcinko]

That was the thing I had to completely disable, due to the huge amount of product categories. It completely broke the search frontend/backend, because the html code was so big, the browser couldn’t handle it.

I’m not sure I can fix that, but I will look at it tomorrow, I need to get some sleep now 🙂

[Ernest Marcinko]

Thanks!

Hopefully I can finally add the fulltext search engine for the next version. That technology is designed especially for big databases like yours. That will work even better!

[Author]

Posts