ad_page_contract (public)
ad_page_contract [ -form form ] [ -level level ] [ -context context ] \ [ -warn ] [ -properties properties ] docstring [ args... ]
Defined in packages/acs-tcl/tcl/tcl-documentation-procs.tcl
Specifies the contract between programmer and graphic designer for a page. When called with the magic "documentation-gathering" flag set (to be defined), the proc will record the information about this page, so it can be displayed as documentation. When called during normal page execution, it will validate the query string and set corresponding variables in the caller's environment.
Example:
An argspec takes one of two forms, depending on whether there's a default value or not:ad_page_contract { Some documentation. @author me (my@email) @cvs-id $Id: tcl-documentation-procs.tcl,v 1.67 2024/12/13 09:40:45 gustafn Exp $ } { foo bar:integer,notnull,multiple,trim {greble:integer {[expr {[lindex $bar 0] + 1}]}} } -validate { greble_is_in_range -requires {greble:integer} { if { $greble < 1 || $greble > 100 } { ad_complain } } greble_exists -requires { greble_is_in_range } { if { ![info exists ::greble_values($greble)] } { ad_complain [_ acs-tcl.lt_Theres_no_greble_with] } } } -errors { foo {error message goes here} bar:integer,notnull {another error message} greble_is_in_range {Greble must be between 1 and 100} }
{name[:flag,flag,flag] default}
name[:flag,flag,flag]
If no default value is specified, the argument is considered required, but the empty string is permissible unless you specify
:notnull
. For all arguments, the filter:nohtml
is applied by default. If the arg is named*.tmpfile
, thetmpfile
filter is applied.Possible flags are:
more filters...
- trim
- The value will be string trimmed.
- notnull
- When set, will barf if the value is the empty string. Checked after processing the
trim
flag. If not set, the empty string is always considered valid input, and no other filters are processed for that particular value. If it's an array or multiple variable, the filters will still be applied for other values, though.- optional
- If there's a default value present, it's considered optional even without the flag. If a default is given, and the argument is present but blank, the default value will be used. Optional and no default value means the variable will not be set, if the argument is not present in the query string.
- multiple
- If multiple is specified, the var will be set as a list of all the argument values (e.g. arg=val1&arg=val2 will turn into arg=[list val1 val2]). The defaults are filled in from left to right, so it can depend on values of arguments to its left.
- array
- This syntax maps query variables into Tcl arrays. If you specify
customfield:array
, then query varcustomfield.foo
will translate into the Tcl array entry$customfield(foo)
. In other words: whatever comes after the dot is used as the key into the array, or, more mathematically:x.y=z => set x(y) z
. If you use dot or comma is part of your key (i.e.,y
above contains comma or dot), then you can easilysplit
on it in your Tcl code. Remember that you can use any other flag or filter with array.- verify
- Will invoke
ad_verify_signature
to verify the value of the variable, to make sure it's the value that was output by us, and haven't been tampered with. If you useexport_vars -form -sign
orexport_vars -sign
to export the variable, use this flag to verify it. To verify a variable namedfoo
, the verify flag looks for a form variable namedfoo:sig
. For a:multiple
, it only expects one single signature for the whole list. For:array
it also expects one signature only, taken on the[array get]
form of the array.- cached
- This syntax will check to see if a value is being passed in for this variable. If it is not, it will then look in cache for this variable in the package that this page is located, and get this value if it exists.
- date
- Pluggable filter, installed by default, that makes sure the array validates as a date. Use this filter with :array to do automatic date filtering. To use it, set up in your HTML form a call to a date formfield. Then on the receiving page, specify the filter using
varname:array,date
. If the date validates, there will be a variable set in your environmentvarname
with four keys:day, month, year,
anddate
. You can safely pass$varname(date)
to Oracle.- time
- Pluggable filter, installed by default, that makes sure the array validates as a time in am/pm format. That is that it has two fields:
time
andampm
that have valid values. Use this filter with :array to do automatic time filtering. To use it, set up in you HTML form using [ec_timeentrywidget varname] or equivalent. Then on the processing page specify the filter usingvarname:array,time
. If the time validates, there will be a variable set in your environmentvarname
with five keys:time, ampm, hours, minutes,
andseconds
.- time24
- Pluggable filter, installed by default, that makes sure the array validates as a time in 24hr format. That is that it has one field:
time
that has valid values. Use this filter with :array to do automatic time filtering. To use it, set up in you HTML form using <input type="text" name="varname".time>. Then on the processing page specify the filter usingvarname:array,time24
. If the time validates, there will be a variable set in your environmentvarname
with four keys:time, hours, minutes,
andseconds
.- integer
- Pluggable filter, installed by default, that makes sure the value is integer, and removed any leading zeros.
- naturalnum
- Pluggable filter, installed by default, that makes sure the value is a natural number, i.e. non-decimal numbers >= 0.
- oneof
- Pluggable filter, installed by default, that makes sure the value X contained in the set of the provided values. Usage example:
color:oneof(red|blue|green)
- range
- Pluggable filter, installed by default, that makes sure the value X is in range [Y, Z]. Usage example:
foo:range(1|100)
- nohtml
- Pluggable filter, installed by default, that disallows any and all html.
- html
- Pluggable filter, installed by default, that only allows certain, safe allowed tags to pass (see ad_html_security_check). The purpose of screening naughty html is to prevent users from uploading HTML with tags that hijack page formatting or execute malicious code on the users's computer.
- allhtml
- Pluggable filter, installed by default, that allows any and all html. Use of this filter is not recommended, except for cases when the HTML will not be presented to the user or there is some other reason for overriding the site-wide control over naughty html.
- tmpfile
- Checks to see if the path and file specified by tmpfile are allowed on this system.
- sql_identifier
- Pluggable filter, installed by default, that makes sure the value is a valid SQL identifier.
- path
- Pluggable filter, installed by default, that makes sure that argument contains only Tcl word characters or a few additional safe characters used in paths ("/", ".", "-")
- token
- Pluggable filter, installed by default, that makes sure that argument contains only Tcl word characters or a few additional safe characters (",", ":", "-").
- word
- Pluggable filter, installed by default, that makes sure that argument contains only Tcl word characters (as defined by \w in Tcl regular expressions, i.e. characters, digits and underscore).
- localurl
- Pluggable filter, installed by default, that makes sure that argument contains a non-external url, which can be used in ad_returnredirect without throwing an error.
- clock
- Pluggable filter, installed by default, that makes sure that argument is a time string formatted according to the format specified in the flag. The format uses the syntax from the clock Tcl command. Usage example time:clock(%H:%M:%S).
Note that there can be no spaces between name, colon, flags, commas, etc. The first space encountered denotes the beginning of the default value. Also, variable names can't contain commas, colons or anything Tcl accepts as list element separators (space, tab, newline, possibly others) If more than one value is specified for something that's not a multiple, a complaint will be thrown ("you supplied more than one value for foo").
There's an interface for enhancing ad_page_contract with pluggable filters, whose names can be used in place of flags (see
ad_page_contract_filter
). There's also an interface for pluggable filter rules, which determine what filters are applied to arguments (seead_page_contract_filter_rule
).Note on QQ-variables: Unlike the old
ad_page_variables
,ad_page_contract
does not set QQ-versions of variables. The QQ-versions (had each single-quote replaced by two single-quotes) were only necessary for building up SQL statements directly in a Tcl string. Now that we're using bind variables, the QQ-variables aren't necessary anymore, and thus,ad_page_contract
doesn't waste time setting them.Default Values
Default values are filled in from left to right (or top to bottom), so it can depend on the values or variables that comes before it, like in the example above. Default values are only used when the argument is not supplied, thus you can't use default values to override the empty string. (This behavior has been questioned and may have to be changed at a later point.) Also, default values are not checked, even if you've specified flags and filters. If the argument has themultiple
flag specified, the default value is treated as a list. If thearray
flag is specified, we expect it to be inarray get
format, i.e. a list of{ name value name value ... }
pairs. If bothmultiple
andarray
are set, thevalue
elements of the before-mentionedarray get
format are treated as lists themselves.Errors Argument
The-errors
block defines custom error messages. The format is a list inarray get
format with alternating error-names and error texts. The error names can befoo
, which means it's thrown when the variable is not supplied. Orfoo:flag,flag,...
, which means it'll get thrown whenever one of the flags fail. If you want the same error to be thrown for both not supplying a var, and for a flag, you can sayfoo:,flag,...
(a comma immediately after the colon).Validation Blocks
The-validate
is used to fully customized user input validation. The format is a list of named chunks of code, for example:-validate { name { code block } another_name -requires { argname[:filter-or-validation-block-name,...] ... } { code block } }The name is for use with the-errors
block, and for use within the-requires
argument of another validation block. The validation blocks will get executed after all flags and filters have been evaluated. The code chunk should perform some validation, and if it's unhappy it should callad_complain
, optionally with an error message. If no error message is specified, the error should be declared in the-errors
section.Each validation block can also have a
-requires
switch, which takes a list of validations that must already have been successfully passed, for the validation to get executed. The intent is that you want to provide as much feedback as possible at once, but you don't want redundant feedback, like "foo must be an integer" and "foo must be in range 10 to 20". So a check for foo in range 10 to 20 would have a-requires { foo:integer }
switch, to ensure that the check only gets executed if foo was successfully validated as an integer.In the
-requires
argument, you can specify a list of (1) the name of an argument, which means that the argument must be supplied. Or (2) you can specifyargname:filter
orargname:validation_block
to say that a given filter, flag or valdiation block must have been executed and satisfied for this validation block to get executed. You can have as many requirements as you like.
- Switches:
- -form (optional)
- Optionally supply the parameters directly here instead of fetching them from the page's form (ns_getform). This should be a reference to an ns_set.
- -level (optional, defaults to
"1"
)- -context (optional)
- -warn (optional, boolean)
- -properties (optional)
- What properties the resulting document will contain.
- Parameters:
- docstring (required)
- The documentation for your page; will be parsed like ad_proc and ad_library.
- Authors:
- Lars Pind <lars@pinds.com>
- Yonatan Feldman <yon@arsdigita.com>
- Bryan Quinn <bquinn@arsdigita.com>
- Created:
- 16 June 2000
- Partial Call Graph (max 5 caller/called nodes):
- Testcases:
- page_contracts
Source code: ad_complaints_init $context #################### # # Parse arguments # #################### set query [list] if { [llength $args] > 0 } { set valid_args { validate errors return_errors properties } ;# add type later # If the first arg isn't a switch, it should be the query if { [string index [lindex $args 0] 0] ne "-" } { set args [lassign $args query] } else { # otherwise, accept a -query argument lappend valid_args query } ad_arg_parser $valid_args $args } # reset $::ad_page_contract_variables if {[info exists ::ad_page_contract_variables]} { unset ::ad_page_contract_variables } #################### # # Check supplied query form and set up variables in caller's environment # #################### # # These are the steps: # 1. go over the formal args, massaging it into an internal data structure that's easier to manipulate # 2. go over the form (actual args), match actual to formal args, apply filters # 3. go over the formal args again: defaulting, post filters, complain if required but not supplied # 4. execute the validation blocks # #################### #################### # # Step 1: Massage the query arg into some useful data structure. # #################### # BASIC STUFF: # list apc_formals list of formals in the order specified by in the arguments # array apc_formal($name) 1 if there is a formal argument with that name # array apc_default_value($name) the default value, if any # # FILTERS: # array apc_internal_filter($name:$flag): 1 if the given flag is set, undefined # array apc_filters($name): contains a list of the filters to apply # array apc_post_filters($name): contains a list of the post filters to apply # array apc_filter_parameters($name:$flag): contains a list of the parameters for a filter # # DOCUMENTATION: # array apc_flags($name): contains a list of the flags that apply # set apc_formals [list] array set apc_formal [list] array set apc_default_value [list] array set apc_internal_filter [list] array set apc_filters [list] array set apc_post_filters [list] array set apc_filter_parameters [list] array set apc_flags [list] foreach element $query { set element_len [llength $element] if { $element_len > 2 } { return -code error [_ acs-tcl.lt_Argspec_element_is_in] } set arg_spec [lindex $element 0] lassign [ad_page_contract_parse_argspec $arg_spec] name flags lappend apc_formals $name set apc_formal($name) 1 if { $element_len == 2 } { set apc_default_value($name) [lindex $element 1] } set flag_list [list] # find parameterized flags foreach flag [ad_page_contract_split_argspec_flags $flags] { # # The following statement is transitional code, and should # help in the upgrading phase, when newer page_contracts # with "object_id" are processed, but the # page_contract_filter_proc is not yet defined. # if {$flag eq "object_id" && [info commands ad_page_contract_filter_proc_object_id] eq "" } { # fall back to "integer" set flag integer ns_log notice "Warning: page contract contains 'object_id', but filter proc is not available" } set left_paren [string first "(" $flag] if { $left_paren == -1 } { lappend flag_list $flag } else { if { [string index $flag end] ne ")" } { return -code error "Missing or misplaced end parenthesis for flag '$flag' on argument '$name'" } set flag_parameters [string range $flag $left_paren+1 [string length $flag]-2] set flag [string range $flag 0 $left_paren-1] lappend flag_list $flag set apc_filter_parameters($name:$flag) [ad_page_contract_split_argspec_flag_parameters $flag_parameters] } } # # Apply filter rules # foreach filter_rule [array names ::acs::ad_page_contract_filter_rules] { [ad_page_contract_filter_rule_proc $filter_rule] $name flag_list } # # Sort the flag list according to priority # set flag_list_for_sorting [list] foreach flag $flag_list { lappend flag_list_for_sorting [list [ad_page_contract_filter_priority $flag] $flag] } set flag_list_sorted [lsort -index 0 $flag_list_for_sorting] # # Split flag_list up into the different kinds, i.e. internal, filter (classic) or post_filter. # # apc_flags($name) is for documentation only. # set apc_flags($name) [list] set apc_filters($name) [list] set apc_post_filters($name) [list] foreach flag_entry $flag_list_sorted { set flag [lindex $flag_entry 1] lappend apc_flags($name) $flag switch [ad_page_contract_filter_type $flag] { internal { set apc_internal_filter($name:$flag) 1 } filter { lappend apc_filters($name) $flag } post { lappend apc_post_filters($name) $flag } default { return -code error "Unrecognized flag or filter \"$flag\" specified for query argument $name" } } } } #################### # # Documentation-gathering mode # #################### if { [api_page_documentation_mode_p] } { # Just gather documentation for this page ad_parse_documentation_string $docstring doc_elements # copy all the standard elements over foreach element { query properties } { if { [info exists $element] } { set doc_elements($element) [set $element] } } # then the arrays foreach element { apc_default_value apc_flags } { set doc_elements($element) [array get $element] } # then the array names set doc_elements(apc_arg_names) $apc_formals # figure out where the calling script is located, relative to the ACS root set root_dir [nsv_get acs_properties root_directory] set script [info script] set root_length [string length $root_dir] if { $root_dir eq [string range $script 0 $root_length-1 ] } { set script [string range $script $root_length+1 end] } error [array get doc_elements] "ad_page_contract documentation" } # # Page serving mode # #################### # # Parse -properties argument # #################### # This must happen even if the query (aka parameters, formals) is empty if { [info exists properties] } { upvar 1 __page_contract_property property array set property [doc_parse_property_string $properties] } # If there are no query arguments to process, we're done if { $query eq "" } { return } #################### # # Parse -validate block # #################### # # array apc_validation_blocks($name): an array of lists that contain the validation blocks # the list will contain either 1 or 2 elements, a possible # list of required completed filters/blocks and the code block # for the validation block. Once the block has executed, this entry # self destructs, i.e. unset apc_validation_blocks($name) array set apc_validation_blocks [list] if { ![info exists validate] } { set validate [list] } set validate_len [llength $validate] for { set i 0 } { $i < $validate_len } { incr i } { set name [lindex $validate $i] if { [string first : $name] != -1 } { return -code error [_ acs-tcl.lt_Validation_block_name] } if { [info exists apc_formal($name)] } { return -code error [_ acs-tcl.lt_You_cant_name_your_va] } if { [info exists apc_validation_blocks($name)] } { return -code error [_ acs-tcl.lt_You_cant_have_two_val] } incr i if { [string index [lindex $validate $i] 0] == "-" } { if { [lindex $validate $i] ne "-requires" } { return -code error [_ acs-tcl.lt_Valid_switches_are_-r] } set requires [lindex $validate [incr i]] foreach element $requires { if { [string first , $element] != -1 } { return -code error [_ acs-tcl.lt_The_-requires_element] } set parts_v [split $element ":"] set parts_c [llength $parts_v] if { $parts_c > 2 } { return -code error [_ acs-tcl.lt_The_-requires_element_1] } set req_filter [lindex $parts_v 1] if { $req_filter in {array multiple} } { return -code error "You can't require \"$req_name:$req_filter\" for block \"$name\"." } } incr i } else { set requires [list] } set code [lindex $validate $i] set apc_validation_blocks($name) [list $requires $code] } #################### # # Parse -errors argument # #################### if { [info exists errors] } { ad_complaints_parse_error_strings $errors } #################### # # Step 2: Go through all the actual arguments supplied in the form # #################### if { $form eq "" } { set form [ns_getform] if {$form eq "" && ![ns_conn isconnected]} { ad_log warning "ad_page_contract called with no form data and no connection; aborting request" ad_script_abort } } # This is the array in which we store the signature variables as we come across them # Whenever we see a variable named foo:sig, we record it here as apc_signatures(foo). array set apc_signatures [list] foreach {actual_name actual_value} [ns_set array $form] { # # Map actual argument to formal argument ... only complication is from arrays # # Check the name of the argument to passed in the form, ignore if not valid if { [regexp -nocase -- {^[a-z0-9_\-\.\:]*$} $actual_name] } { # The name of the formal argument in the page set formal_name $actual_name # This will be var(key) for an array set variable_to_set var # It may be a signature for another variable if { [regexp {^(.*):sig$} $actual_name match formal_name] } { set apc_signatures($formal_name) $actual_value # We're done with this variable continue } # If there is no formal with this name, _or_ the formal that has this name is an array, # in which case it can't be the right formal, since we'd have to have a dot and then the key if { ![info exists apc_formal($formal_name)] || [info exists apc_internal_filter($formal_name:array)] } { # loop over all the occurrences of dot in the argument name # and search for a variable spec with that name, e.g. # foo.bar.greble can be interpreted as foo(bar.greble) or foo.bar(greble) set found_p 0 set actual_name_v [split $actual_name "."] set actual_name_c [expr { [llength $actual_name_v] - 1 }] for { set i 0 } { $i < $actual_name_c } { incr i } { set formal_name [join [lrange $actual_name_v 0 $i] "."] if { [info exists apc_internal_filter($formal_name:array)] } { set found_p 1 set variable_to_set var([join [lrange $actual_name_v $i+1 end] "."]) break } } if { !$found_p } { # The user supplied a value for which we didn't have any arg_spec # It might be safest to fail completely in this case, but for now, # we just ignore it and go on with the next arg continue } } if { [info exists apc_internal_filter($formal_name:multiple)] && $actual_value eq "" } { # LARS: # If you lappend an empty_string, it'll actually add the empty string to the list as an element # which is not what we want continue } # Remember that we've found the spec so we don't complain that this argument is missing ad_page_contract_set_validation_passed $formal_name # # Apply filters # if { [info exists apc_internal_filter($formal_name:trim)] } { set actual_value [string trim $actual_value] ad_page_contract_set_validation_passed $formal_name:trim } if { $actual_value eq "" } { if { [info exists apc_internal_filter($formal_name:notnull)] } { ad_complain -key $formal_name:notnull [_ acs-tcl.lt_You_must_specify_some] continue } else { ad_page_contract_set_validation_passed $formal_name:notnull } } else { set ::ad_page_contract_validations_passed($formal_name:notnull) 1 foreach filter $apc_filters($formal_name) { set ::ad_page_contract_errorkeys [concat $formal_name:$filter $::ad_page_contract_errorkeys] set filter_proc [ad_page_contract_filter_proc $filter] if { ![info exists apc_filter_parameters($formal_name:$filter)] } { set filter_ok_p [$filter_proc $formal_name actual_value] } else { set filter_ok_p [$filter_proc $formal_name actual_value $apc_filter_parameters($formal_name:$filter)] } set ::ad_page_contract_errorkeys [lrange $::ad_page_contract_errorkeys 1 end] if { $filter_ok_p } { set ::ad_page_contract_validations_passed($formal_name:$filter) 1 } else { break } } } # # Set the variable in the caller's environment # upvar 1 $formal_name var if { [info exists apc_internal_filter($formal_name:multiple)] } { lappend $variable_to_set $actual_value } else { if { [info exists $variable_to_set] } { set complaint [_ acs-tcl.lt_Youve_supplied_two_va] ad_complain -key $formal_name:-doublevalue $complaint ad_log warning "User experienced '$complaint' when submitting a form related to path_info: [ad_conn path_info]" continue } else { set $variable_to_set $actual_value } } } else { ad_log warning "ad_page_contract: attempt to use a nonstandard variable name in form: '$actual_name'" } } #################### # # Step 3: Pass over each formal argument to make sure all the required # things are there, and setting defaults if they're provided, # apply post filters, and validate signatures. # #################### foreach formal_name $apc_formals { upvar $level $formal_name var if { [info exists apc_internal_filter($formal_name:cached)] } { if { ![ad_page_contract_get_validation_passed_p $formal_name] && ![info exists apc_internal_filter($formal_name:notnull)] && (![info exists apc_default_value($formal_name)] || $apc_default_value($formal_name) eq "") } { if { [info exists apc_internal_filter($formal_name:array)] } { # This is an array variable, so we need to loop through each name.* variable for this package we have ... set array_list "" foreach arrayvar [ns_cache names util_memoize] { if {[regexp [list [ad_conn session_id] [ad_conn package_id] "$formal_name."] $arrayvar]} { set arrayvar [lindex $arrayvar [llength $arrayvar]-1] if { $array_list ne "" } { append array_list " " } set arrayvar_formal [string range $arrayvar [string first "." $arrayvar]+1 [string length $arrayvar]] append array_list "{$arrayvar_formal} {[ad_get_client_property [ad_conn package_id] $arrayvar]}" } } set apc_default_value($formal_name) $array_list } else { set apc_default_value($formal_name) [ad_get_client_property [ad_conn package_id] $formal_name] } } } # # Perform these checks only, when the validation is passed and # a we have a value for the variable # if { [ad_page_contract_get_validation_passed_p $formal_name] && [info exists var]} { if { [info exists apc_internal_filter($formal_name:verify)] } { if { ![info exists apc_internal_filter($formal_name:array)] } { # This is not an array, verify the scalar variable if { ![info exists apc_signatures($formal_name)] || ![ad_verify_signature -secret [ns_config "ns/server/[ns_info server]/acs" parameterSecret ""] $var $apc_signatures($formal_name)] } { ad_complain -key $formal_name:verify [_ acs-tcl.lt_The_signature_for_the] continue } } else { # This is an array: verify the [array get] form of the array if { ![info exists apc_signatures($formal_name)] || ![ad_verify_signature -secret [ns_config "ns/server/[ns_info server]/acs" parameterSecret ""] [lsort [array get var]] $apc_signatures($formal_name)] } { ad_complain -key $formal_name:verify [_ acs-tcl.lt_The_signature_for_the] continue } } } # Apply post filters foreach filter $apc_post_filters($formal_name) { ad_complaints_with_key $formal_name:$filter { set filter_proc [ad_page_contract_filter_proc $filter] if { ![info exists apc_filter_parameters($formal_name:$filter)] } { set filter_ok_p [$filter_proc $formal_name var] } else { set filter_ok_p [$filter_proc $formal_name var $apc_filter_parameters($formal_name:$filter)] } } if { $filter_ok_p } { ad_page_contract_set_validation_passed $formal_name:$filter } else { break } } } else { # # No value supplied for this arg spec. # if { [info exists apc_default_value($formal_name)] } { # # Only use the default value if there has been no # complaints so far Why? Because if there are # complaints, the page isn't going to serve anyway, # and because one default value may depend on another # variable having a correct value. # if { [ad_complaints_count] == 0 } { # we need to set the default value if { [info exists apc_internal_filter($formal_name:array)] } { array set var [uplevel subst \{$apc_default_value($formal_name)\}] } else { set var [uplevel subst \{$apc_default_value($formal_name)\}] } } } elseif { ![info exists apc_internal_filter($formal_name:optional)] && ![info exists ::ad_page_contract_validations_passed($formal_name)] } { # # The element is not optional and it was not already # flagged by the notnull constraint. # # Before we complain, we check, if a multirow or array # with the name are already defined in the target # environment. This is just used for cases, where # multirows are passed to an "ad_include # contract". These data types are not copied to the # ns_set and therefore these are not seen by the above # tests. No further checking other than check for # existence is performed for these cases. # set multirow_name $formal_name:rowcount if {![uplevel $level [list info exists $multirow_name]] && ![uplevel $level [list info exists $formal_name]] } { ad_complain -key $formal_name [_ acs-tcl.lt_You_must_supply_a_val] } } } } #################### # # Step 4: Execute validation blocks # #################### set done_p 0 while { !$done_p } { set done_p 1 foreach validation_name [array names apc_validation_blocks] { lassign $apc_validation_blocks($validation_name) dependencies code set dependencies_met_p 1 # # Check, of the variables of the dependencies were provided. # foreach dependency $dependencies { set varName [lindex [split $dependency ":"] 0] if { ![ad_page_contract_get_validation_passed_p $varName] } { # var $varName was not provided set dependencies_met_p 0 break } } # # Check, whether the earlier section haven't returned # errors, in which case the detailed validation is not # necessary. # if { $dependencies_met_p && [ad_complaints_count] > 0} { set dependencies_met_p 0 } if { $dependencies_met_p } { # remove from validation blocks array, so we don't execute the same block twice unset apc_validation_blocks($validation_name) set no_complaints_before [ad_complaints_count] # Execute the validation block with an environment with a default error key set set ::ad_page_contract_errorkeys [concat $validation_name $::ad_page_contract_errorkeys] set validation_ok_p [ad_page_contract_eval uplevel 1 $code] set ::ad_page_contract_errorkeys [lrange $::ad_page_contract_errorkeys 1 end] if { $validation_ok_p eq "" || ($validation_ok_p ne "1" && $validation_ok_p ne "0" ) } { set validation_ok_p [expr {[ad_complaints_count] == $no_complaints_before}] } if { $validation_ok_p } { set ::ad_page_contract_validations_passed($validation_name) 1 # more stuff to process still set done_p 0 } } } } #################### # # Done. Spit out error, if any # #################### # Initialize the list of page variables for other scripts to use set ::ad_page_contract_variables $apc_formals if { [ad_complaints_count] > 0 } { set complaints [ad_complaints_get_list] if {$warn_p} { ad_log warning "contract in '$::ad_page_contract_context'" "was violated:\n" [join $complaints "\n "] } if { [info exists return_errors] } { upvar 1 $return_errors error_list set error_list $complaints } else { template::multirow create complaints text foreach elm $complaints { template::multirow append complaints $elm } ad_try { if {[ns_conn isconnected] == 0} { ad_script_abort } if {[incr ::__ad_complain_depth] == 1} { # # Render the error page going through templating, # theming and so on. # # This is the intended complaint behavior, where # the page will look "fancy" and consistent with # the rest of the website. # set context $::ad_page_contract_context set prev_url [util::get_referrer -trusted] set html [ad_parse_template -params [list complaints [list context $context] prev_url] [template::themed_template "/packages/acs-tcl/lib/complain"]] } else { # # We detected a recursion. This can happen if the # templates involved in rendering the complaint # also fail their own validation. # # We fallback to a basic rendering that won't # involve any other template in order to break the # cycle. # ad_log warning "Depth of recursive complaints exceeded. We will return a basic rendering." set html [subst { <html> <head> <title>[_ acs-tcl.lt_Problem_with_your_inp]</title> </head> <body> <ul> <li>[join $complaints </li><li>]</li> </ul> </body> </html> }] } } on error {errorMsg} { set errorCode $::errorCode # # Check, if we were called from "ad_script_abort" (intentional abortion) # if {[ad_exception $errorCode] eq "ad_script_abort"} { # # Yes, this was an intentional abortion # return "" } ad_log error "problem rendering complain page: $errorMsg ($errorCode) $::errorInfo" set html "Invalid input" } ns_return 422 text/html $html ad_script_abort } }XQL Not present: Generic, PostgreSQL, Oracle