//FIXME: all the values in the $aAttribs list used to go thru sm_encode_html_special_chars()... I would propose that most everything that is assigned to the template should go thru that *in the template class* on its way between here and the actual template file. Otherwise we have to do something like: foreach ($aAttribs as $key => $value) $aAttribs[$key] = sm_encode_html_special_chars($value);
$oTemplate->assign('aAttribs', $aAttribs);
return $oTemplate->fetch('input.tpl');
}
/**
* Password input field
* @param string $sName field name
* @param string $sValue initial password value
* @param integer $iSize field size (number of characters)
* @param integer $iMaxlength maximum number of characters the user may enter
* @param array $aAttribs (since 1.5.1) extra attributes - should be given
* in the form array('attribute_name' => 'attribute_value', ...)
//FIXME: all the values in the $aAttribs list and $sName and both the keys and values in $aValues used to go thru sm_encode_html_special_chars()... I would propose that most everything that is assigned to the template should go thru that *in the template class* on its way between here and the actual template file. Otherwise we have to do something like: foreach ($aAttribs as $key => $value) $aAttribs[$key] = sm_encode_html_special_chars($value); $sName = sm_encode_html_special_chars($sName); $aNewValues = array(); foreach ($aValues as $key => $value) $aNewValues[sm_encode_html_special_chars($key)] = sm_encode_html_special_chars($value); $aValues = $aNewValues; And probably this too because it has to be matched to a value that has already been sanitized: $default = sm_encode_html_special_chars($default); (oops, watch out for when $default is an array! (multiple select lists))
$oTemplate->assign('aAttribs', $aAttribs);
$oTemplate->assign('aValues', $aValues);
$oTemplate->assign('bUsekeys', $bUsekeys);
$oTemplate->assign('default', $default);
$oTemplate->assign('name', $sName);
$oTemplate->assign('multiple', $bMultiple);
$oTemplate->assign('size', $iSize);
return $oTemplate->fetch('select.tpl');
}
/**
* Normal button
*
* Note the switched value/name parameters!
* Note also that regular buttons are not very useful unless
* used with onclick handlers, thus are only really appropriate
* if you use them after having checked if JavaScript is turned
* on by doing this: if (checkForJavascript()) ...
*
* @param string $sValue button name
* @param string $sName key name
* @param array $aAttribs extra attributes
*
* @return string html formated submit input field
*
* @since 1.5.2
*/
function addButton($sValue, $sName = null, $aAttribs=array()) {
$aAttribs['value'] = $sValue;
if (! is_null($sName)) $aAttribs['name'] = $sName;
// add default css
if (! isset($aAttribs['class'])) $aAttribs['class'] = 'sqmsubmitfield';
//FIXME: all the values in the $aAttribs list as well as $sName and $sText used to go thru sm_encode_html_special_chars()... I would propose that most everything that is assigned to the template should go thru that *in the template class* on its way between here and the actual template file. Otherwise we have to do something like: foreach ($aAttribs as $key => $value) $aAttribs[$key] = sm_encode_html_special_chars($value); $sName = sm_encode_html_special_chars($sName); $sText = sm_encode_html_special_chars($sText);
$oTemplate->assign('aAttribs', $aAttribs);
$oTemplate->assign('name', $sName);
$oTemplate->assign('text', $sText);
$oTemplate->assign('cols', (int)$iCols);
$oTemplate->assign('rows', (int)$iRows);
return $oTemplate->fetch('textarea.tpl');
}
/**
* Make a <form> start-tag.
*
* @param string $sAction form handler URL
* @param string $sMethod http method used to submit form data. 'get' or 'post'
* @param string $sName form name used for identification (used for backward
* compatibility). Use of id is recommended instead.
* @param string $sEnctype content type that is used to submit data. html 4.01
* defaults to 'application/x-www-form-urlencoded'. Form
* with file field needs 'multipart/form-data' encoding type.
* @param string $sCharset charset that is used for submitted data
* @param array $aAttribs (since 1.5.1) extra attributes
* @param boolean $bAddToken (since 1.5.2) When given as a string or as boolean TRUE,
* a hidden input is also added to the form containing a
* security token. When given as TRUE, the input name is
* "smtoken"; otherwise the name is the string that is
* given for this parameter. When FALSE, no hidden token
* input field is added. (OPTIONAL; default not used)
//FIXME: all the values in the $aAttribs list as well as $charset used to go thru sm_encode_html_special_chars()... I would propose that most everything that is assigned to the template should go thru that *in the template class* on its way between here and the actual template file. Otherwise we have to do something like: foreach ($aAttribs as $key => $value) $aAttribs[$key] = sm_encode_html_special_chars($value); $sCharset = sm_encode_html_special_chars($sCharset);