[Sommaire] [Imprimer]

   1  -------------------------------------------------------------------------------
   2  Mantis - a php based bugtracking system
   3  Copyright (C) 2000-2002  Kenzaburo Ito - kenito@300baud.org
   4  Copyright (C) 2002-2004  Mantis Team   - mantisbt-dev@lists.sourceforge.net
   5  -------------------------------------------------------------------------------
   6  
   7  CONFIGURATION
   8  
   9  * Also see configuration.html
  10  
  11  This file contains information to help you customize Mantis.  A more
  12  detailed doc can be found at:
  13  http://manual.mantisbugtracker.com/manual.customizing.mantis.php
  14  
  15  * config_defaults_inc.php
  16    - this file contains the default values for all the site-wide variables.
  17  * config_inc.php
  18    - You should create this file to change config variable values.  Your
  19      values from this file will be used instead of the defaults.  This file
  20      will not be overwritten when you upgrade, but config_defaults_inc.php will.
  21      Look at config_inc.php.sample for an example.
  22  
  23  * core/*_api.php - these files contains all the API library functions.
  24  
  25  * global variables are prefixed by g_
  26  * parameters in functions are prefixed with p_
  27  * form variables are prefixed with f_
  28  * variables that have been cleaned for db insertiong are prefixed with c_
  29  * user related variables are prefixed with u_
  30  * other variables are usually either prefixed with v_ or t_
  31  * count variables have the word count in the variable name
  32  
  33  More detail can be seen in the coding guidelines at:
  34  http://www.mantisbugtracker.com/guidelines.php
  35  
  36  Also at:
  37  http://utvikler.start.no/code/php_coding_standard.html
  38  
  39  * The files are split into three basic categories, viewable pages,
  40  include files and pure scripts. Examining the viewable pages (suffix _page)
  41  should make the basic file format fairly easy to see.  The file names
  42  themselves should make their purpose apparent.  I decided to break the
  43  work into many small files rather than have a small number of really
  44  large files.
  45  
  46  * Most of the action scripts have a confirmation page to make sure the action
  47  completed successfully.  The pages will automatically redirect you after a
  48  short amount of time.  You can shorten of lengthen the time by editing
  49  $g_default_redirect_delay in config_inc.php.
  50  
  51  * Edit css_inc.php to make your own page formatting.
  52  
  53  * You can edit the print_header() and print_footer() functions in core_API.php
  54    to alter what should be visible at the top and bottom of each page.
  55  
  56  * All files were edited with TAB SPACES set to 4.  I'm sorry if this causes
  57  a problem, but I can't stand 8 (wastes space) and tabs are helpful.  I've
  58  tried to alleviate this in the config file by using spaces for the most part.
  59  
  60  *** A note on globals: globals are a rather quirky item in php.  Basically
  61  all variables are always local in scope unless declared global.  This is why
  62  some of the include() files have global declarations in them.
  63  
  64  As a general debugging tip you should be extremely generous in using echo,
  65  print and exit functions.  This is the quickest way to see if a database
  66  query actually contains what you want, etc.