[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Thank you very much!

That worked just fine. I managed to find a possible bug. The document had over 100 000 keywords, which is fairly long, and for some reason a loop was stuck on processing the keywords.
I changed it to a different one, and that immediately improved the loop performance from about 50 seconds to 0.02 seconds, so it is as expected now. The document should be now properly indexed.

I will make sure to include this fix in the upcoming release.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Thank you Daniel!

I checked, and the live search results were actually all right, so that means that the results page override was not actually in effect – I am guessing you might be using some sort of a custom content plugin or a custom loop of some sort to the results page.
Anyways, enabling the query soft check option seems to have resolved the issue and Ajax Search Pro now forces it’s results to the results page.

[Ernest Marcinko]

1. Sure, you can use a custom CSS, something like:

@media only screen and (max-device-width: 480px){
   .asp_sett_scroll {
      max-height: unset !important;
   }
}

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

Sure! This will do the trick:

form.asp-fss-flex {
    justify-content: center;
}

[Ernest Marcinko]

Hi,

Thank you for the details!

Generally WordPress database tables are case and accent insensitive by default. These issues in most cases need to be resolved on the host, by converting the underlying database to a case and accent insensitive one (which should be the default). Some things can be forced via the plugin, I will check if there is anything I an do.

Unfortunately I can’t login. Both the admin and the wp-login pages give me an internal server error when I try to reach them. Can you please check?

[Author]

Posts