Post Processing

Phorm™ v3.5.2

Post Processing:

If you wish, you can have a file with PHP code that will be processed after Phorm has done everything else (or aborted on an error). Simply define $PHORM_POSTINC with the name of the file. It will be processed at the very end, just before any errors are displayed to the visitor and/or alerts emailed to you; thus, you can modify these if you wish, or perform other actions based on how the program executed. Note that this file will always be executed if $PHORM_POSTINC is set, regardless of what occurred in the program -- it is up to you to determine what actions you want to take. Some internal variables that may be of interest to you are:

$ph_Abort		`True` if there was a fatal error.
$ph_Alerts		An associative array containing alert codes and messages. The index is a three-digit code, and the value is the message. The symbol `%%%` in the text of the message will be replaced with the alert code. Alert and Error codes and messages are summarized in Appendix C.
$ph_Errs		An associative array containing error codes and messages. The index is a three-digit code, and the value is the message. The symbol `%%%` in the text of the message will be replaced with the error code.
$ph_Redirect		A URL to re-direct to, set either to $PHORM_URL by the $PHORM_RCONFIG code, or to $PHORM_RDIRECT.
$ph_Invals		A comma-separated list of the rule numbers that failed validation.
$ph_ValErr		True if a data validation error occurred
$ph_ErrLevel		Data validation error level
$ph_ValMsg[]		An array of validation error messages read in from the rules file, indexed by error level. Thus, $ph_ValMsg[$ph_ErrLevel] will contain the message(s) actually displayed to the visitor.

A list of all of Phorm's internal variables is contained in the file docs/internals.txt in the distribution.

0101000001101000011011110111001001101101010010010111001101000011011011110110111101101100