Forum Replies Created
-
Posts
-
Oh, I see, let me check the code then.
What happens if you only type in 1 word? Like “ajax” or something else. In case of search terms with multiple words in it, does it give you the same result order if you change the words order? Like “ajax javascript” opposed to “javascript ajax” and similar? I’m very curious.
Hi Eno!
Thank you very much for recommending my plugin!
The secondary ordering kicks in when the relevance is exactly the same. The problem is that the search does not count the occurrences of the words (it could, but it would kill the performance), so in this case the occurrence does not matter.
Fulltext might take this into account, but then again the relevance values are not adjustable there.
I’ll try to consult with the folks on stackoverflow to see if anyone knows an efficient way of counting string occurrences without inflicting the performance greatly. This would definitely benefit the search greatly.
Until then, the only solution I can suggest is to use the priority submenu to prioritize more inportant posts.
Hi!
You can change all of these in the Theme Options -> Isotopic Resluts tab: Result width, Result height and Rows count: https://i.imgur.com/kj2G7Bx.png
The results/row is calculated based on the width of the container and the Result width.
Hi!
I’ve managed to solve it with the ftp. I think you might have updated from an older version to 4.0 or a database inconsistency might have happened.
Anyways, this was a partially known problem and you can always use this guide for safely updating the plugin: http://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/update_notes.html
The cache options were missing for some reason. I’m making a few changes for the upcoming version, so these problems should never appear again 😉
Hi!
That is because this is programaticaly not possible unfortunately. There is no way of mixing logics between distinctive fields within the WordPress database.
The AND/OR logic only works on each field separately. I’m sorry, if there was any way of making this even with modifications, I would gladly do it for you, but unfortunately it’s not possible.
Hi!
There is an option there to turn off the exact mathing, with an explanation: http://i.imgur.com/Oz4WhY6.png
That way products matching at least one of the tags will be treated as related.
On the Advanced options panel you can exclude terms. (scroll down, almost on the bottom)
Hi!
I can only support you on workdays, on the weekends my family needs me, sorry about that.
1. You can disable search in posts and pages, which is enabled by default, and select the songs custom post type to search.
In this chapter of the documentation you can find how to disable search posts and pages.
In the next chapter there is a description on how to select other custom post types to search for.2. Slow ajax response in most cases is not related to the search, there are many factors influencing the search speed.
Please read the Performance tuning section and the tips & tricks section on how to increase your site performance.Moreover I did run some tests on your site, and there is something definitely clogging the ajax responses (not only ajax search, but every ajax operation).
Look at this test. The performance tracker shows that the search is finished after 0.2 seconds in reality. However most likely something else (another plugin or theme etc..) is keeping your server busy, because the results appear only after 14!! seconds, and that’s the same exact query on both screenshots. That means that something is most likely making 70 times more operations before or after the search is finished.
Try to disable all the plugin and switching the theme and check if it improves the performance, it definitely should. If not, then I might need ftp access as well to check if there is any connection for the slowdown with the search plugin.
Interestingly, repetitive search shows various performance. I’ve got results for the search term “test a” in 14 seconds, then in 2.5 seconds for the second time, then 5.5 seconds for the third time, then 2.5 seconds for the fourth time. Is it possible that your hosting provider might throttle your server performance? I don’t see any other explanation on why the same exact term delays 14 seconds, then only 2.5 seconds.
Hi!
Thank you for the proper details! It was a simple variable name conflict. I’ve made a minor change to the plugin code to fix this. I will however create another long term solution for the upcoming plugin update.
Hi!
1. Could you please upload screen shots of the settings you applied and the results you are not expecting to see?
Have you excluded the proper terms on the advanced options panel? You can check the documentation here.
If you can give me examples maybe I can tell if there is anything wrong with the configuration or so 😉2. Could you please be more specific about this issue? Are you using the search results shortcode somewhere on the same page where the search is?
The plugin can not (because it’s not possible in WordPress) overwrite the themes result layout, if that’s what you mean. The results page (where the default wordpress search redirects) in your theme can only be edited by editing your theme unfortunately.Non-latin characters would be an issue if you would get no results at all, but that’s a very rare issue and it’s related to a bad database collation. In your case that’s not the problem for sure.
The documentation explains almost every single detail accordingly, starting from how to create a search engine to the more advanced options.
I’m working more than 80 hours a week on my plugins and support alone to make them better, unfortunately I couldn’t find any time to make video tutorials yet, but it’s planned of course.
Hi!
Please read the related articles on this topic in the documentation:
http://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/performance_tuning.htmlHi!
Yes, it had been approved 3 hours ago. You should be able to download the plugin from codecanyon. You will probably get an email about the update as well, I suppose envato is not sending it immediately.
Hi!
1. On the Theme Options -> Magnifier & Loading icon panel: http://i.imgur.com/jL9uoYJ.png
2. Most likely only by editing your theme and inserting the shortcode. (unless there is a widgetizable area available under the menu)
Hi!
It’s white because it’s most likely overriden by your theme. I suggest the following CSS instead, it should help:
[code]
.searchsettings,
.searchsettings * {
color: #fff999 !important;
}
[/code]You can add this to the Theme Options -> Custom CSS panel 😉
Hi!
I see the problem now. “Aigen Lehen” does not match a single tag. Each tag is treated separately, because they are stored separately in the database.
The search logic “AND” in this case means that looks for tags that match both “aigen” and “lehen”.I know it would be logical as you described, and I have experimented with different approaches, but currently it’s not possible because of the following reasons:
1. With a simple concatenation method the performance would drop extremely – by extreme I mean 10 to 1000 times slower depending on tags count
2. The only applicable solution is to create a separate index table to avoid the previously mentioned slowdown at least on some levelThe good news is that I’m working on an index table, which is going to be an optional feature and it will solve this and other logical issues as well. It will however take some time until I finish all tests and find the final and best structure – but this is going to happen sooner or later.
As a temporary solution I would do the following:
1. Create a post meta field with the tags for the downloads, for example with the name “search_keywords”
2. Copy/paste the tags there as well, like: “tag1, tag2, tag3…”
3. Select this field to search, instead of terms on the search plugin General Options -> Sources panel.But of course after creating 1-2 you should check if it works as you expected, not to waste time.
This is good because it’s much less performance heavy as searching in terms, as in this solution, all the tag names are stored in one single field per post.
