According to Malcolm Austen:
> On Thu, 31 Aug 2000, Gilles Detillieux wrote:
> + According to Malcolm Austen:
> + > I only need to pass one string through but someone will want more! Could
> + > we have, say, USER_STRING_<digit> as a hidden input field option to be
> + > passed through into search results just like restrict and exclude and
> + > available for substitution as $(USER_STRING_n)
> + 
> + allow_in_form: user_string_1
> + 
> + will take the user_string_1 input parameter, and use it to set the
> + user_string_1 config attribute and the USER_STRING_1 template variable.
> + Yes, you can define your own arbitrary input parameters, config
> + attributes and template variables in this way - you're not restricted
> + to the pre-defined ones.  You can choose any name you want, e.g.
> + "header_string" or anything else you think is appropriate.
> 
> Oh, that's much too easy! 8-) I'm afraid I read too many restrictions into
> what I could do with allow_in_form.

What restrictions did you read into it?  Can we make the documentation
for allow_in_form clearer somehow to avoid this confusion?  Suggestions
are welcome.

-- 
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 htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
List archives:  <http://www.htdig.org/mail/menu.html>
FAQ:            <http://www.htdig.org/FAQ.html>

Reply via email to