Question
The %SEARCH{}% function does not work within
TWikiGroups. It does not list any groups. How can I find out the reason for this problem?
Environment
--
ThomasKurz - 26 Apr 2006
Answer
If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.
If SEARCH doesn;t work
anywhere, check that you have a GNU-compatible grep installed and selected in
configure. Search problems in Solaris are usually a result of the wrong grep being used.
Assuming that you have got SEARCH working
somewhere, check that you actually have some groups defined. The topics need to end in "Group" and the line
* Set GROUP = is required. Then, check that the user who is trying to list the groups has VIEW access to all the group files.
--
CrawfordCurrie - 26 Apr 2006
This might be a different issue. The SEARCH in TWikiGroups is a topic search, e.g. grep is not involved. Not sure though what can cause this. Try
WebSearch, with scope on "Text body" and then "Topic title" to test which one works.
--
PeterThoeny - 27 Apr 2006
The Result of
WebSearch is that only the "Topic title" search works. With the configure script I get warnings for 'fgrep' and 'egrep' that they are not GNU: illegal option.
Could this be the reason for the not working "Text body" search?
--
ThomasKurz - 27 Apr 2006
You need a GNU compatible grep. This is certainly why
WebSearch isn't working. Peter is right about the search in TWikiGroups; it is a topic search. i have no idea why it isn't working (assuming it is still failing).
--
CrawfordCurrie - 27 Apr 2006
Just checked, TWikiGroups has a search on text body, not topic name (
%SEARCH{"GROUP" topic="*Group" ...}%), e.g. your normal text body search does not work because you do not have a GNU compatible grep.
--
PeterThoeny - 28 Apr 2006
After installation of GNU grep the SEARCH function works. Thank you for the support.
I think it would be better to list GNU compatible fgrep, egrep under TWiki Server Requirements instead of fgrep, egrep. Shouldn't the configure script show an error message instead of a warning if grep was detected which is not compatible with GNU grep?
--
ThomasKurz - 28 Apr 2006