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 +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 +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 users. The name of each each user is linked back to the same page, -with the appropriate user_id. The page prompts the +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.
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 +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.
Try the following scenarios: