Why does Index CCK Node Reference depend on FuzzySearch?
cailinanne - September 23, 2007 - 15:42
| Project: | Index CCK Node Reference |
| Version: | 5.x-0.1-beta1 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
First, much thanks for writing this module!! I had recently made a decision to have ContentTypeX have a node reference field to my Country table, instead of just having a text field called Country. I had a moment of panic when I realized this might mess up my ability to do a keyword search of ContentTypeX for the country, and then a bigger moment of panic when I realized I was right! I was most pleased to discover that you had already solved my problem.
Question : why does this module depend on FuzzySearch? It seems to be integrated perfectly with normal Search. I don't want FuzzySearch, and was forced to install and enable it to get Index CCK Node Reference to work with normal Search.
Is that just a typo in your dependency list?
#1
Yes, I should remove that, I actually had created this module while creating my Fuzzy Search module and didn't really think about it too much I guess. I'll release an update today.
#2
Thanks very much.
I had not realized you were also the Fuzzy Search author. Since you are, I will also explain why I am not using Fuzzy Search. As far as I could tell
1. The Search module exposes a field to the Views module, "Search : Index".
2. The Fuzzy Search module does not expose any field to the Views module.
If you don't mind, please let me know if this is incorrect.
#3
Is there an ETA for addressing this issue?
#4
just edit the .info file and remove the dependencies line