In any form you create, or any constructed URL, you must be sure to include this param as part of the form so that the right response can be matched up for the submitted data. For example:

<form> [% self.CGI.hidden(self.config_state_param) %] First name:[% self.CGI.textfield("first_name") %]<br> Last name: [% self.CGI.textfield("last_name") %] <input type=submit> </form>

You should change this if you are using mod_perl to something that won't conflict with other usages of the same server space. For CGI scripts, the default is an easy classname to remember.

Note that the template also use this name as their prefix, so that your controller and template files end up in the same directory.

If you change "config_class_prefix", you'll want to change this as well so that "WRAPPER.tt" ends up in the right directory. (I debated doing that for you so you could just say "WRAPPER.TT", but that'd make more complicated versions of this callback be even more and more complicated.)

The wrapper template is called with "template" set to the wrapped template, which should be processed in the wrapper. The smallest wrapper is therefore:

  [% PROCESS $template %]
    

However, typically, you'll want to define app-wide blocks and variables, and maybe wrap the statement above in an exception catcher. For example:

  [%-
  TRY;
    content = PROCESS $template;
    self.CGI.header;
    self.CGI.start_html;
    content;
    self.CGI.end_html;
  ### exceptions
  ## for errors:
  CATCH;
    CLEAR;
    self.CGI.header('text/plain');
  -%]
  An error has occurred.  Remain calm.
  Authorities have been notified.  Do not leave the general area.
  [%-
    FILTER stderr -%]
  ** [% template.filename %] error: [% error.info %] **
  [%
    END; # FILTER
  END; # TRY
  -%]
    

This sends back a plain message to the browser, as well as logging the precise error text to "STDERR", and hopefully the web error log.

Called with a page name, returns a new page object that can be used as "self" in a template, mixing in the code from the page's class for additional heavy lifting.

For example, to have a "subpage" plugin, create a "subpage.tt" and "subpage.pm" file, then include the tt with:

  [% INCLUDE My/App/subpage.tt
       self = self.plugin("subpage")
       other = parms
       go = here
  %]
    

Now, within "subpage.tt", calls to "self.SomeMethod" will first search the original page's lineage, and then the plugin class lineage for a definition for "SomeMethod".

If you have site-wide buttons (like a button-bar on the side or top of your form), look for them in "respond_per_app", and return the new page from there. Otherwise, return "undef", and it'll fall through to the per-page response.

  Template->new
    (
     POST_CHOMP => 1,
     INCLUDE_PATH => [@INC],
     COMPILE_DIR => $self->config_compile_dir,
     PROCESS => [$self->config_wrapper],
    )