Index: openacs-4/packages/acs-tcl/tcl/utilities-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-tcl/tcl/utilities-procs.tcl,v diff -u -r1.133.2.6 -r1.133.2.7 --- openacs-4/packages/acs-tcl/tcl/utilities-procs.tcl 9 Sep 2013 09:11:34 -0000 1.133.2.6 +++ openacs-4/packages/acs-tcl/tcl/utilities-procs.tcl 9 Sep 2013 10:11:54 -0000 1.133.2.7 @@ -491,7 +491,7 @@
This will export the three variables foo
, bar
and baz
as
- hidden HTML form fields. It does exactly the same as [export_vars foo bar baz]
.
+ hidden HTML form fields. It does exactly the same as [export_form_vars foo bar baz]
.
@@ -887,7 +887,7 @@ Example: -
+doc_body_append [export_vars { msg_id $user(email) { order_by date } }]
will export the variabledoc_body_append [ad_export_vars { msg_id user(email) { order_by date } }]
msg_id
and the value email
from the array user
,
and it will export a variable named order_by
with the value date
.
@@ -908,7 +908,7 @@
A more involved example:
+doc_body_append [ad_export_vars -override { order_by $new_order_by } $my_vars] @param form set this parameter if you want the variables exported as hidden form variables, as opposed to URL variables, which is the default. @@ -1020,7 +1020,7 @@ export_vars is now the prefered interface.set my_vars { msg_id user(email) order_by } -doc_body_append [export_vars -override { order_by $new_order_by } $my_vars]
- Example usage: [export_vars -sign foo bar:multiple baz]
+ Example usage: [export_form_vars -sign foo bar:multiple baz]
@param sign If this flag is set, all the variables output will be
signed using