Please read this entire file before asking for assistance. Thank you.

There is now a support forum available on the Phorm site at 
http://www.phorm.com/

If you are having difficulties with Phorm, please execute the phpinfo.php3 
script (rename it to phpinfo.php if you're running PHP4) in the same directory 
you have Phorm installed in, and send me the resulting page when asking for 
assistance. This will help greatly in locating your trouble. If possible, it's 
best to save the actual HTML page that's output, and send it to me as an 
attachment, rather than simply copying and pasting the text. It's much easier to 
read.

                         ----------------------------
                                 Debug Flags
                         ----------------------------
Phorm has a number of debug flags built in, which will cause it to display 
various information about its operation. When you're having trouble with a
particular operation, try setting the flag or flags related to it, and see if 
that sheds any light on the situation. To set a flag, assign the TRUE value
to it in your configuration file. For example, to set debug flag 8 (display
mail template names), you would put this line in your configuration file:

  $ph_debug8 = TRUE;

The debug flags are:

  1   = Display alerts always
  2   = Report major segments
  3   = Report minor segments
  31  = Display various settings
  32  = Test plugins
  33  = Display plugins
  34  = Report stages
  35  = Report variable substitutions
  41  = Display ValDefs input
  411 = Display ValDefs Criteria
  412 = Display form fields found in the error form
  52  = Display responder mail function paramemters
  71  = Display MySQL database variables
  72  = Display MySQL Query
  8   = Display mail template name(s)
  81  = Display mail template lines
  812 = Display expanded template lines
  82  = Display user mail function parameters
  9   = Display file upload parameters

                         ----------------------------
                                 MySQL Logging
                         ----------------------------
If you are using a version of PHP prior to 3.0.6, you may have problems if you 
are using the MySQL logging feature, and the data you are logging contains the ' 
character (single quote, also known as apostrophe). If you are getting a MySQL 
error, try adding the following line to your configuration file:

$PHORM_QUOTES = True;

                         ----------------------------
                              Regular Expressions
                         ----------------------------
Phorm uses a pattern-matching technique call regular expressions in order to 
find the {{variable}} pattern for variable substitution. However, some 
installations of PHP use a different regular expression library. If you are 
having problems with variable substitution not working, or if you're getting 
warnings about a { or } character, for example: 

    Warning: Invalid content of \{\} in....

there is an internal variable you can set to select a different expression. 
Add the following line to your config file:

$PHORM_REGEX = 1;

You can also try settings 2-13 if that doesn't work. With settings over 6, you 
will not be able to use indexed variables (arrays) for variable substitution. 
For settings 6 and 13, you will have to use << >> for your variable 
substitutions rather than {{ }}.

                         ----------------------------
                                Tab Characters
                         ----------------------------
If you're creating your phormbase.txt file or validation rules file with an 
editor that won't let you use a tab character (I've heard they exist), there is 
a mysterious internal variable buried deep in the heart of Phorm, named 
$ph_config_delim. It is set to a tab character -- change it to whatever you'd 
like. Look around line 390.

                         ----------------------------
                                 How can I. . .?
                         ----------------------------
If your question starts with "How can I. . .?", be sure to check out Appendix A 
in the documentation first; many of the tips there came from users asking such 
questions. If you don't find your answer there, go ahead and ask -- maybe I'll 
include it in the next version of the docs!