"Start parsing" button  top

Starting parsing proccess for form-file from the "File to process" field. Three options are available:

•  "Ignore old settings, fresh parsing" and "Use this variables file" are OFF:
     FSave will parse the file from begin or load forms data from old variables file if exists
  
•  "Ignore old settings, fresh parsing" is ON:
    FSave will parse source file from begin and ignore old settings from variables file even if exist
  
•  "Cross with this variables file" is ON, Variables field contains :
     FSave will load forms data from another variables file (for more information see above).
  
  
  EXAMPLE: you'd like to parse /form_test.php with variables from /test_form.prs.php (already exists).
  Let assume that form_test.php contains Form1 form with a1, a2, a3 fields and Form2 and test_form.prs.php contains data about Form1 with a1,o1,a3 fields. Then FSave will load form_test.prs.php and test_form.prs.php and fill settings for Form1 and add a1,a3 fields from additional variables file test_form.prs.php to main data (filled from form_test.prs.php)

SP, Include, CGI model radiogroup  top

SP.Engine can manage input of data in a form in three modes:

• SP mode
  There is only mode if you will use SP.TE on the same page
  That mode is equal to Include, but SP.TE makes caching and calls form's parser. I.e:
  
  [FORM__test ... ]
  <form name='test' action='form_file.php'>
  ...
  </form>
  [END__FORM__test]
  
  You can use form in Edit mode, use another templates fileds in the form and use form fields in another templates
  
•  CGI mode
  - Form parser is called through action
  <form name='test' ... action='/sp/fcss.php' ... >
  
•  INCLUDE mode
  - Form parser call is hidden by php output control functions. Example:
  
  <?ob_start();?>
  <form name='test' action='form_file.php'>
  ...
  </form>
  <?include "/sp/fcss.php";?>
  
  then form parser loads source, caches output and prints parsed output back to browser
  
  $fcss_source = ob_get_contents();
  ob_end_clean();
  
  

Errors output: Language  top

Choose output language for errors. There are english and portuguese (thanks to Luis P. Sousa, lpmac.com) languages right now
But you can easily make your own translation
There are special files like language.translation.php in SP folder. Just copy one of them, rename "language" part (for instance, myown.translation.php) and translate. Then SP.DE adds your translation file into this select
$checking_message["SS"] - Server side output messages
$checking_message["CS"] - Client side output messages
Error phrase can include three special fileds -
FNAME - field name
FMUST - correct value
FWRONG - entered value

Errors output: Position  top

Set position for server side error message relative to field: Above, Left, Right, Under
If you use form-file page in SP mode you can set a place for output error messages with {ERROR__fieldname} tag
Parser will ignore Error output position and prints error message in place of {ERROR__fieldname}
It's better to use {ERROR__} tag with [] operator because {ERROR__} will become empty {} in case of No error
And [] cuts off in case it includes empty {}.
I.e. [<span class="special">You'v make the error - {ERROR__fieldname}</span>]

"Thank you" page  top

If you want to redirect your form results to confirmation ("thank you") page, but need other than default output template - enter file name here.

IMPORTANT: Confirmation page must contains form with the same name as you could miss some inputs couse parser checks if fields exist in working on file and fill them.

MySQL part  top

SP.DE could load data entered through the form into MySQL table

Firstly, you need to set MySQL access. There are two ways to use this function.

• To set all DB access values - Host, DB Name, DB user, Password, Table.
• Create file db.inc.php
  <?
  $FS_form["DBHost"] = "localhost";
  $FS_form["DBLogin"] = "login";
  $FS_form["DBPass"] = "pass";
  $FS_form["DBName"] = "dbname";
  ?>
  and place the file into form's file directory. DBTable loads from variables file anyway
  
  Choose at least one data field to be saved into table. FSave is trying to pick right choice in column "Type".

• NO MySQL - don't save this field into MySQL table. Default value for submit button.
• COUNTER - short name for INTEGER AUTOINCREMENT
• BOOL - in fact it's TINYINT (1) UNSIGNED. Default for checkboxes. If checked - save 1, otherwise - save 0
• INT - UNSIGNED INTEGER
• SIGNINT - SIGNED INTEGER
• FLOAT - same as in MySQL
• TIME - same as in MySQL
• DATE - same as in MySQL
• YEAR - same as in MySQL
• DATETIME - same as in MySQL
• TIMESTAMP - same as in MySQL
• CHAR - depends on Size - CHAR or VARCHAR. Default for text, password inputs, select
• TEXT - same as in MySQL. Default for TEXTAREA
• ENUM - same as in MySQL, values list must be present in Values. Default for radio button
• SET - same as in MySQL, values list must be present in Values.
  
  COUNTER, INT, SIGNINT, CHAR, TEXT actual MySQL type depends on Size. For instance, INT up to 256 will be TINYINT (3). Actual type printed in View fields box

As a rule, each table has data part and keys part that helps the script to build the structure of the database.

Example: you have a script for customers to access restricted part of your site, your tables contain USER_ID field and ID of logged-in users, saved into SESSION variables or maybe transfers into hidden variable. You can set FCSS to save user ID into MySQL table - just use Key fields editor.

But if you want to hidde some table's fields and do not show them on your form, FSave will generate an error message - use Key fields editor to load values for such fields.

DB User  top

User name that has access to MySQL Database you set above
User must have correct permissions to access MySQL database, so be sure you have created the database, created the database user, and added the user to the database (edited users permissions).

"Insert IF" & "Update IF" selects  top

You can set one of form's field and optional value as a flag to add/update record. It means that SP.DE will add/update if field you set will exist in form values - isset($_POST [field] ), and if you set а value - be equal to - $_POST [field] = 'key_value' :

•  To make SP.DE will add record only when some checkbox was set (or some button was used to post a form) - choose this field name from the "Insert IF" pop-up menu.
•  To make SP.DE will update record only when some checkbox was set (or some button was used to post a form) - choose this field name from the "Update IF" pop-up menu.
  
  Generally speaking, SQL DBs updates record via phrase like UPDATE filed=val,... WHERE keyfield=key.
  So, to update a table by form's data, related table must have a key field and a variable with the key must exist while form's data will be posted. In fact, the key can be transfered via $_POST, $_SESSION arrays.
  
  You can use Key fields editor to create the key field and set a source for key val.
  But when you set a field in "Update IF", FSave checks and creates key field 'ID'(COUNTER) if ommited. FSave also checks and creates a source for key val as $_POST ['ID'] if ommited. That is, a hidden field 'ID' with key as a value must be in the form.
  If you use form-file in SP mode, FSave adds such field after <form ...>. Then you only need to fill the form with SP.TE tags.
  
•  To use the same form-file to add and to update records, choose one field for Insert action and another one - for Update.
  Example: add two submit buttons in the form, name one of your submit button as "Insert" and another one
  as "Update", parse form through FSave.php. If you have parsed form already - set "Reparsing" checkbox. Select "Insert" button for Insert IF and "Update" button for Update IF. Then if customer hit "Insert" - SP.DE will add record and if hit "Update" will update record. Assume that you set keys as described above.