I have used Trip Search for a while now and when I upgraded to drupal 4.7 I saw the announcement that Trip Search was no longer going to be developed. Please don't stop. I like Trip Search better than the integrated 4.7 search and would like to continue using it. If there's a feature I'd like, it'd be to upgrade Trip Search to work with 4.7.

Thank you!

Comments

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Thanks for your interest. I'm glad the module has been useful.

My personal judgement is that the considerable development time that would be required to upgrade, maintain, and improve trip search would be much better directed to improving the core search, which has a superior architecture. Users should be encouraged to migrate to the core search. If there are pieces missing from the core search, the model is extensible and they can be added.

If another developer were to step forward and present a proposal to maintain trip search through the 4.7 cycle, I would of course be happy to talk.

joel_guesclin’s picture

joel_guesclin commented

Actually, I could be interested in taking this over. I still prefer trip_search to the new search module, for a number of reasons:
a) most important, it uses full text indexes standard to the database, rather than building up its own indexes
b) as per the above, it doesn't depend on cron to index, and all documents are indexed automatically as soon as they are added to the site
c) you have more options to exclude search options that you don't want to have appear

I'm currently working on updating it for 4.7, ironing out bugs as I go along (eg phrases between double-quotes not working, access to comments not working, exclusions only working on inclusive result sets, etc etc)

However, I'm not a great PHP guru and my site's needs are more limited than others perhaps, so there are a number of things that my new trip_search won't have:
a) it will ONLY work on fulltext search (using "basic search" nearly caused my hosting service to boot me out); and I only intend to code the MySQL part - Postgre uses REGEXP to do indexed full text searches and I propose to leave that in so someone else could contribute that, however I don't plan to support Postgre myself. I may later get round to trying out natural language as well as boolean mode, depending on the results i get
b) it won't use the "comments" and "statistics" tables (no searching in comments) at least not in a first release

joel_guesclin’s picture

joel_guesclin commented
Status: Active » Closed (fixed)

I've posted some news about the module.