According to Geoff Hutchison:
> > Another question: is it possible to enter the restrict and exclude
> > lines by hand?
>
> If you're using a wrapper, you could probably format the data for a POST
> method. However, I also think you should be able to set the restrict and
> exclude lines via config file since the CGI takes the input and puts it
> into the config object. I believe if you don't specify restrict and
> exclude to the CGI, it will end up defaulting to the config versions.
Unfortunately, this is one of the inconsistencies in input parameter
handling in htsearch that remains to be resolved. For restrict and
exclude, it does indeed set config attributes of the same name, but
it only uses these for setting the template variables. For building
the actual StringMatch objects that it uses to test the URLs, it only
looks at the input parameters. This would need to be changed. The
flow of data should be something like this:
input parameter config file attribute
--------------- ---------------------
| | (override compiled default)
| v
| config object before input checked
| |
v v
input object ---(override)--> config object ---> template vble
| |
v v
page list button URL value actually used
Not all input parameters currently follow this model.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
