Changes between Version 1 and Version 2 of TracFormsPlugin/Expert


Ignore:
Timestamp:
May 1, 2011, 1:18:36 AM (13 years ago)
Author:
Steffen Hoffmann
Comment:

start documenting the env_debug operation

Legend:

Unmodified
Added
Removed
Modified

  • TracFormsPlugin/Expert

    v1 v2  
    66!TracForms has a way to allow multiple forms within a parent resource (ticket description or wiki page): the ''subcontext''.
    77Using multiple unique ''subcontext'' IDs you can define a virtually unlimited number of independent forms per parent resource.
    8 Add the ''subcontext'' command with an argument into the form header like this:
     8Add the ''subcontext'' command with an argument into each form header like this:
    99{{{
    1010{{{
    … …  
    1616}}}
    1717}}}
    18 Here we set the subcontext to the id 'different_form'.
    19 This helps the form markup parser find saved field values and know where to put form update information for this form.
     18Here we set ''subcontext'' to the ID 'different_form'.
     19This helps the form markup parser/processor to find saved field values and to know where to put field update information for this form.
     20You'll notice, if you failed to comply with this demand for distinct form IDs:
     21Each update of one form will reset other form fields within the same (unset) subcontext.
     22
     23== Debug print ==
     24There is a debug operation to reveal any value of the corresponding !TracForm environment.