Forum Replies Created
-
Posts
-
Hi Benny!
I’ve been trying to access the page you have given in your ticket but I’m getting the page with the following image only: http://i.imgur.com/RFrVTpa.png
Hi Vikki!
Would you mind checking it now? There is another method implemented into the plugin, which I activated now and the conflicting file is not included anymore.
Indeed, some requests were slower than expected.
I have modified the search algorithm file to a current test version, which should be faster. Currently I’m testing on the test page you provided, so far the results appear much fastear (in ~2 seconds)
However I can still see longer requests from time to time, which might indicate that your server needs more resources. I’ve tried for example the same search term several times, but the response times varied from 1 to 10 seconds. The request times went up drastically when I opened the back end of the site. If your traffic went up, you should definitely consider using a faster hosting plan. The search performance tracker also showed interesting values – the same requests took 0.09 seconds, then 5.3 seconds, then 2 seconds, then 0.09 seconds again.
This was also visible when refreshing some of the pages – sometimes it was quick, sometimes it took 10 or more seconds.Anyways, the update I provided should make the responses faster, but I recommend checking if the hosting plan limits are enough.
Also, there are a few tips you can find in the documentation, which might be useful for performance tuning: http://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/performance_tuning.html
Let me know if you have any questions.
Hi!
The issue had been resolved in your other ticket 🙂 I’m closing this one, please use the other one if you need anything.
Hi!
There was an error generated because you are using an earlier wordpress version. I’ve made a correction in the plugin code to fix this, but I highly suggest updating to the latest wordpress version, as there was a critical bug discovered earlier this month in the WordPress core.
Hi!
It looks like one of the plugins was using the BFI_thumb library as well, but an older version. I’ve added an extra line to prevent the collision, the error messages should be gone. I’m adding this fix to the upcoming version just to make sure it won’t happen to anyone else 🙂
Hi!
The problem is that the search is contained within DIV elements, which are rendered as block types. Blocking elements are acting as container blocks, so they are placed on top of each other.
It’s hard to tell only by the screenshot if the buttons are in the same container as the search bar, and if their container is a block or an inline element.
You can try this custom CSS, but I have no idea if this is going to work, because as I said, it depends on search bar placement and button placement:
[code].ajaxsearchpro.asp_main_container {
display: inline-block !important;
}[/code]..and you might also need to force exact width, but I’m not sure:
[code].ajaxsearchpro.asp_main_container {
display: inline-block !important;
width: 300px !important;
}[/code]Hi!
Sorry, it looks like I missed your ticket by accident.
I’m not sure which version of the plugin are you using, but based on your buyer data I’m guessing 3.5. If so, then please download it again from codecanyon and proceed to update to version 4.0. There are a few safe-update steps described in the first chapter of the new documentation, which I suggest to follow.
I remember someone else had a similar issue, and I’ve changed up a few things in this new version, so I hope this will fix this problem. If the update does not change anything, then let me know and we figure out something else.
Hi!
I cannot login to the back-end of the site, I’m getting this error:
[code]Fatal error: Call to undefined function get_home_path() in /home/racinne/public_html/wp-admin/includes/misc.php on line 16[/code]
Perhaps this is related to the search issue? The error is coming from a WordPress core file, you should definitely check, it might lead to other errors as well.
Hi!
No, it should show, unless the keyword logic is set to “OR with exact word matches” or “AND with exact word matches”. In that case “360” does not mach “360dialog” as a single word. Same might happen with fulltext search, as it usually ignores numbers. If the result does show up for “0dialog” or “60dialog” and the keyword logic is not set for exact word matches then most likely fulltext is being used.
Exact matches mean, that in case of multiple keywords they are treated as one word and there is no search query with them separately.
Hi Stefan!
The Sroll the window to the result list? option was active on the Layout Options -> Results behavior panel, that caused the problem. Luckily I didn’t have to modify anything, but for the upcoming version I’ll add an exception to the code to ignore this option in compact mode.
Plus I noticed that the checkboxes in the settings dropdown were overwritten by the theme CSS so I added this custom CSS to the search Custom CSS panel to slolve this problem:
[code]
.searchsettings .option label:before {
display: none !important;
}
[/code]Hi!
It looks like that on your test server the fulltext search class is called, at least that’s what I see from the response content. This might be an unknown bug yet, I don’t know.
Would you please try to open up the Fulltext search settings submenu and save the options? You can even change them a few times to make sure the input values change. I’ve checked the relevance code, but it looks all right to me, so this might be the problem I guess.
