I posted a bug report about the full_text search not working and since then there seem to have been some patched posted about this. Problem - when I look at the patches, they all seem to be based on 4.7 (inclusion of node_revisions table amongst other things).
Is there a patched version for 4.6.0? I could really seriously use this - or even just the patches would do and I could apply them myself.
Also, I am dubious about whether the actual bug I reported has been properly fixed...
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | trip_search_0.module | 45.18 KB | joel_guesclin |
Comments
Comment #1
lzfranc commentedOnly to confirm that I am having the same problem, but if it is being worked to Drupal 4.7 it is a good news.
Comment #2
joel_guesclin commentedProblem is that - according to the developers - trip_search is not being ported to 4.7 because a lot of its functionality has been moved into core search. Consequently there is no hope of the bugs in 4.6 being fixed nor will there be a port to 4.7. In addition all the
In order to try to resolve this problem, I have gone through the 4.6 version of trip_search and done some quick hacks: these are partly to resolve existing problems, partly to get rid of things that I did not need and that I feared might be slowing down my site (my host service complained about the resources I was using). I've attached the modified version of the module, in the hope that it might be useful but BE AWARE that the changes made here are only QUICK HACKS to make the module work with my configuration - it might not work for you. Here are the changes done:
1) The reason that there is a problem returning zero results using mySQL Fulltext indexing is that the WHERE clause is not generated correctly. This is due to the link to the comments module, but also to the fact that trip_search searches in attached file names (the files table). Since I don't use the comments module I left that part alone, but commented out the file names search.
2) There is a bug in the "exclusion" option (ie only results WITHOUT the search keys). Looking at the mySQL manual, the code used to exclude results with the entered key words excludes FROM THE RESULT SET. For example, if I use a keyword "bees" and include an exclusion on "honey", then the result set will include all the articles about bees which do NOT mention honey. On the other hand, if I ONLY include the exclusion on "honey", then the result set will be empty, and NOT all the articles in the site which do not mention "honey". Not having the time to debug this properly, I simply removed the option altogether.
Comment #3
joel_guesclin commentedTry in 4.7