At 17:49 29/05/2002 +0200, Zdenek Pizl wrote:

Dne st 29. kvìten 2002 17:37 jste napsal(a):

...

At 16:20 29/05/2002 +0200, Zdenek Pizl wrote:

...

Hallo,

i am struggling with problem of empty result page while searching mailist archive. Do i have missing some templates or is there some "hack" to be done?

                                                            with

regards

Z. P.

Not a lot to go on in trying to determine what is causing your problem.

First, there is no undocumented "hack" to getting the mailman-htdig patches working that I am aware of. Most of the "hacking" is documented in the $build/INSTALL.htdig-mm that the 444884 patch adds.

Thanks for your response. I managed it to work. I had to slightly modify /etc/htdig-mailman/archive.conf - common_dir and search_results_wrapper directives was added. I noticed that there was no newline character after the last line of directives (but i think that was my mistake).

OK, everything is working fine. The only thing is that i have to create my own templates to suit mailman visual style ...

                                                            thanks

Z.P.

Just a point of clarification. Are you using the Mailman-htdig integration patches 444879 and 444884 posted on sourceforge?

If not ignore what follows.

If so the way you describe as fixing the problem will not last.

The link in htdig's CONFIG_DIR directory (looks like its /etc/htdig-mailman in your case) is a symbolic link to a directory in Mailman's file structures: $prefix/archives/htdig. This directory in turn contains one symbolic link per archived mailing list. These links point to $prefix/private/<listname>/htdig/<listname>.conf respectively, these being the per list htdig conf files.

Each Mailman list has its own htdig configuration file which is automatically generated by the code added to Mailman when the first message is posted to that list after installation of the patch.

[If you want to know why things are organized this way then think about dealing with the issue of security for private archives under search and the need to isolate list search indexes for lists from each other.]

The way you have fixed the problem will only apply to the list whose htdig conf file you have edited. I doubt you want to have a career editing these htdig conf files as a new one is created for each new archived mailing list on your system.

You really want to get at the root of your problem which is what is wrong with your htdig installation such that htsearch cannot find the default htdig COMMON_DIR. The ./configure and make install for htdig should have branded this information into the htsearch CGI program. For the sake of your future sanity I strongly suggest you take a hard look at your htdig installation and correct what has gone wrong.

If you are really determined not to fix the htdig side of things then it is possible to change the code that generates the htdig conf files for the lists to try and compensate. If you want I'll point you in the direction of the source code to change but at that point you'll have to be your own support person for the revised code.

...

I'll assume you got a list which has archiving turned on, has had posts to it since the integration patches were installed and archiving was turned on, and either you or cron have subsequently run the $prefix/cron/nightly_htdig script. As a consequence, I'll assume that the search form has been added to the TOC page for this list and its in response to completing and submitting that form that you are getting an empty page response.

You do not say whether you've used htsearch other that via the Mailman list TOC forms and whether it has worked or not. No matter.

One possible problem may be with your htdig installation. htsearch will try and use the various templates in htdig's COMMON_DIR as defined during installation of htdig (see http://www.htdig.org/htsearch.html) to render its response. It is possible that some problem in configuring or installing htdig may mean that htsearch cannot find the templates in htdig's COMMON_DIR and this is the cause of the problem.

If this SWAG doesn't help then you'll need to supply a bit more information to help track down the problem.