Index: openacs-4/packages/acs-templating/www/doc/guide/search.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/guide/search.adp,v
diff -u -r1.2.2.2 -r1.2.2.3
--- openacs-4/packages/acs-templating/www/doc/guide/search.adp 22 Jun 2016 07:48:44 -0000 1.2.2.2
+++ openacs-4/packages/acs-templating/www/doc/guide/search.adp 5 Jul 2016 12:14:22 -0000 1.2.2.3
@@ -5,6 +5,9 @@
Forms
Form designers are often confronted by the need to provide users
with a way to choose from hundreds or even thousands of potential
options, exceeding the practical capacity of a select list or set
@@ -36,24 +39,24 @@
includes two different forms: Say the administrator wishes to edit the name and screen name of
-a user. The administrator requests a page, user-edit.acs.
-The page looks for a query parameter named user_id to
-specify which user to edit. Initially, user_id is not specified. In this case, the
-page includes a user search form. The user enters part of a user name or screen name and submits
+a user. The administrator requests a page,
+user-edit.acs. The page looks for a query parameter
+named user_id to specify which user to edit. Initially, user_id is not specified. In this case,
+the page includes a user search form. The user enters part of a user name or screen name and submits
the form, which returns to the same URL with the query parameter
user_search. If this parameter is defined, the page
-queries the database for potential matches. If one match is found, the page sets a user_id variable
-and includes the actual user edit form. If multiple matches are found, the page includes a listing of
+queries the database for potential matches. If one match is found, the page sets a user_id
+variable and includes the actual user edit form. If multiple matches are found, the page includes a listing of
users. The name of each each user is linked back to the same page,
with the appropriate user_id. The page prompts the
administrator to choose one. A link is also provided with no
user_id so that the administrator may search again. If the administrator chooses a user, the page detects the
user_id and displays the edit form. A working implementation of this example is provided in the
-files demo/user-edit.tcl and demo/user-edit.adp.
-You must execute the demo data file (demo/demo.sql) for
-the page to function.Implementing Search-and-Select Forms
+
+Templating System : User
+Guide
Try the following scenarios: