[geeklog-users] Geeklog's search function
vfuria at gmail.com
Wed Jan 16 11:43:22 EST 2008
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
On Jan 16, 2008 3:43 AM, Saurabh Bhasin <saurabh at bhasin.in> wrote:
> 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.
> geeklog-users mailing list
> geeklog-users at lists.geeklog.net
More information about the geeklog-users