OpenInteract

 view release on metacpan or  search on metacpan

doc/sample-server-perl.html  view on Meta::CPAN

       default_template   => 'base_box::main_box_shell',
       default_separator  => undef,
       default_method     => undef,
       system_box_handler => '%%WEBSITE_NAME%%::Handler::SystemBoxes',
       system_box_method  => '',
       custom_box_handler => '',
       custom_box_method  => '',
     },

     ########################################
     # Login Information
     #
     #
     # Define login information. In the future you'll be able to define
     # the object(s) used for logging in and possibly more.
     #
     # crypt_password: Set whether you want to store encrypted passwords in
     # the database (set by default and recommended). Note that if you're
     # using LDAP or some SMB authentication you want to set this to '0'
     # since the backend will take care of that for you.
     #
     # *_field: These are the fields used to read in the username and
     # password from the user and are used in the 'login_box' component
     # shipped with OpenInteract and found in the 'base_box' package. Note
     # that if 'remember_field' is not defined then we don't display the
     # checkbox in the login box.
     #
     # custom_login_*: Class and method that specify an action that
     # executes when a user logs in (Optional)
     #
     # always_remember: if true then we always remember the login (and
     # don't display the checkbox)

     'login' => {
       crypt_password       => 1,
       login_field          => 'login_login_name',
       password_field       => 'login_password',
       remember_field       => 'login_remember',
       custom_handler       => undef,
       custom_method        => undef,
       custom_fail-method   => undef,
       always_remember      => 0,
     },

     ########################################
     # Display 
     #
     # Various simple miscellaneous display items can go here

     'display_info' => {
        show_redirect_message => 0,
     },

     ########################################
     # Page Directives
     #
     # Page directives come before the rest of the URL and
     # control some fundamental aspect of display. For instance,
     # 'NoTmpl' before a URL will not put the content in a
     # template, and 'Popup' before a URL will put the content
     # into the template used for popup windows (usually a really
     # simple one that you set in your theme). For all directives
     # except the 'No' ones the key  should be found as the value
     # in 'template_names' below which matches up to a key in the
     # theme. (Slightly confusing.)

     'page_directives' => {
       'Popup'      => 'simple_template', 
       'NoTemplate' => 1,
       'NoTmpl'     => 1,
     },

     ########################################
     # Template Key -> Name Mapping
     #
     # Define the keys under which we store our important
     # template names in a theme. This way we can use simple
     # keywords to refer to the page definition templates. (NOTE:
     # This is not used quite yet but should be implemented
     # shortly.)

     'template_names' => {
       'main'   => 'main_template',
       'simple' => 'simple_template',
     },

     ########################################
     # Template Processing
     #
     # Define information used by the template processing modules. 

     'template_info' => {

       # Extension for template files -- used to lookup files by
       # the TT provider module (shouldn't need to change).

       'template_ext' => 'tmpl',

       # cache_size: How many templates the Template Toolkit should
       # cache in memory

       'cache_size' => 75,

       # If true, will remove all compiled files on server restart
       # (production boxes can set this to false so that startup costs
       # aren't so heavy)

       'compile_cleanup' => 1,

       # Extension for compiled TT files. Most people won't (or
       # shouldn't) care about this.

       'compile_ext' => '.ttc',

       # Custom handler that's called before the template object is
       # initialized. Here you can define a PRE_PROCESS template (for
       # instance, with BLOCKs having all your common widgets) or set
       # any of the other configuration information specified in
       # 'perldoc Template::Manual::Config'. If you use this, set
       # 'custom_init_class' to a class that has a method specified in
       # 'custom_init_method' or use the default ('handler')



( run in 0.847 second using v1.01-cache-2.11-cpan-364913b4093 )