[geeklog-users] Geeklog's search function

[Web Site Master]

To remove search results it would be easier to just remove the two functions
from the plugin than edit the core Geeklog code.  Look in the plugins
functions.inc file for these 2 functions.

plugin_searchtypes_pluginnamehere

plugin_dopluginsearch_pluginnamehere


Tom


-----Original Message-----
From: geeklog-users-bounces at lists.geeklog.net
[mailto:geeklog-users-bounces at lists.geeklog.net] On Behalf Of Saurabh Bhasin
Sent: January-17-08 3:17 AM
To: Using Geeklog
Subject: Re: [geeklog-users] Geeklog's search function

Vinny,

Thanks for the response, and explanation into how to proceed further.

I'm probably going to have to talk to Blaine, I guess since i'm mainly  
concerned about the search results from filemgmt and forum plugins. At  
the least, if i can understand how the search works for both of these  
plugins, i will be able to set better expectations for my users, to  
start with. I do think we can improve the search though. I've tried to  
sift through google and various forums but i've not really seen anyone  
else brought this up before?

I've also tried various searches on sites running GL (like  
geeklog.net, portalparts, macosxhints etc) and those "seem" to what  
i'd expect from a search. That leads to me think if i'm doing  
something wrong.

Also, is there any way to control the API behavior (i guess by editing  
search class file is one way) to allow/disallow what is returned from  
a search. Maybe it's a feature request :)

I'm open to ideas but i'll pursue this matter further with Blaine off- 
list.
Thanks again,
-Saurabh

On Jan 16, 2008, at 8:43 AM, Vincent Furia wrote:

> Saurabh,
>
> I can't help you directly with this problem, but I wanted to give you
> some details on how Geeklog's search works so you can better
> troubleshoot the problem.  Each plugin is responsible for handling its
> own search. So the search algorithm for the filemgmt plugin might be
> completely different than for the static pages plugin.  Even the
> "paging" of search results is handled by the individual plugins
> through the plugin search API.
>
> This design has several advantages, such as allowing each plugin to
> search those fields that are appropriate and ordering results in a way
> that may make more sense.  The downside, which you seem to be
> encountering, is that the search results aren't of consistent quality
> for the different plugins.
>
> My suggestion would be to contact the the developer of each plugin you
> are seeing problems with the search.  If you have problems with the
> "core" plugins' search results (static pages, stories, polls, links),
> let us know here and we'll look into the problem.
>
> Many of the plugin developers do read this list though, so if you
> email back with the specific plugins that you're having problems with
> that will give us a place to start.  I hope this email was a little
> helpful.
>
> -Vinny
>
> On Jan 16, 2008 3:43 AM, Saurabh Bhasin <saurabh at bhasin.in> wrote:
>> Hi,
>>
>> Hope someone can help out here. I'm running GL 1.4.1, and have been
>> for quite a while without any issues. After gaining some popularity
>> among the users this site is catering to, i've heard numerous reports
>> that the search function is not quite optimal. When users search  
>> for a
>> phrase or a term, they're presented with pages and file results that
>> don't have anything to do with what they looked for. If it helps, I'm
>> also using filemgmt, forum, and dokuwiki plugins.
>>
>> Also, another oddity is that the file listings keep getting displayed
>> (when users keep clicking on "More..." towards the bottom of the  
>> page)
>> even if they're not related to what was searched. I know this might  
>> be
>> a little vague and i'm willing to provide any/more info. Please let  
>> me
>> know what else i should provide to narrow down the root cause, if  
>> any.
>>
>> Also, if it turns out if this will have to be pursued as a  
>> consulting/
>> paid opportunity, i can discuss that as well after some basic
>> troubleshooting/analysis of root cause.
>>
>> Thanks, and regards.
>> -Saurabh
>> _______________________________________________
>> geeklog-users mailing list
>> geeklog-users at lists.geeklog.net
>> http://eight.pairlist.net/mailman/listinfo/geeklog-users
>>
> _______________________________________________
> geeklog-users mailing list
> geeklog-users at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-users

_______________________________________________
geeklog-users mailing list
geeklog-users at lists.geeklog.net
http://eight.pairlist.net/mailman/listinfo/geeklog-users

__________ NOD32 2800 (20080117) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com