Hello,
I'm currently working on adding a search feature in nahoWikiPlugin.
For this, I would like to simply depend on sfLucenePlugin.
I've integrated it this way :
* Added behavior (wrapped in "if (class_exists('sfLucene', true))").
* Defined a custom indexer to handle relations properly.
* Added a "search.yml" in "nahoWikiPlugin/config/" which defines
sfLucene's index named "wiki".
* Eventually I could add a _searchResult partial that could be easily
overwritten by final user.
Then if I set "app_lucene_index" to "wiki", and go to "http://site/
sfLucene", it works perfectly.
Everything seems well, but I still have an issue : If final user
already uses sfLucene for other cases, he won't use an index named
"wiki". How can I make this really ready to use AND adaptable to any
user's situation ?
I was thinking about using a dynamic key in search.yml (instead of
"wiki: ..." it would be something like "<?php echo
nahoWikiConfiguration::getLuceneIndexName() ?>: ...") but I want to
know if there is a better solution.
Is there a way for sfLucene to merge different indexes in one ?
Thanks for your help !
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---
