- INSTALL_URL
URL that is the home of the installation.
- CVS_WEB
Location of your cvs web interface (see format_comments() in bug.php). This is for links to files in CVS generated from the comments attached to bugs.
- DB_TYPE
The type of database server you are using, according to PEAR's naming convention. Possible choices are fbsql, ibase, ifx, msql, mssql, mysql, oci8, odbc, pgsql, and sybase. Note that only MySQL, PostgreSQL and Oracle 8 have been tested with phpBugTracker
- DB_HOST
The hostname of the database server.
- DB_DATABASE
The name of the database to be used.
- DB_USER
Username to use for connecting to the database.
- DB_PASSWORD
The password to use for connecting to the database.
- ADMIN_EMAIL
The email address that will be used for all correspondence to and from the bug tracker.
- ENCRYPT_PASS
When true, passwords will be stored as an md5() hash in the database. When false, they will be stored as plaintext.
If this is set to true, a new password will be generated for users if they request their password to be emailed to them, as the encryption is not reversible.
- THEME
The directory below the templates directory (both in the top directory and the admin directory) where the HTML template files are located. This makes it easy to wrap the bug tracker in a completely different look.
- STYLE
The CSS file to be used from the styles directory. This makes it easy to change the color scheme and other CSS properties.
- USE_JPGRAPH
Whether to use the JpGraph graphing class for some reports.
- MASK_EMAIL
If true, then email addresses will be shown as example at example dot com. Otherwise, email addresses will be shown as example@example.com.
- HIDE_EMAIL
If true, email addresses will be shown as ****** to users who are not logged in (to help avoid spam bots on public bug trackers). If false, email addresses will be shown according the setting of MASK_EMAIL, above.
- USE_SEVERITY_COLOR
Whether to color the rows of the bug list according to the severity of the bugs. The severity colors can be set via the admin interface. If this is false, the bugs will be listed with alternating background colors of white and gray.
- EMAIL_IS_LOGIN
If true, then users login with their email address, and the email address is shown for fields such as Assigned To and Reported By. If false, the login is not tied to the user's email address.
- STRICT_UPDATING
If set to true, the only people who can make changes to a bug are the reporter, the owner, and those with manager or admin permissions.
- NEW_ACCOUNTS_DISABLED
If set to true, newaccount.php is disabled and only admins can create new accounts.
- ATTACHMENT_PATH
The subdirectory in which to store bug attachments. This directory needs to writeable by the web server.
- ATTACHMENT_MAX_SIZE
Maximum size (in bytes) of an attachment. This will not override the settings in php.ini if php.ini has a lower limit.
- DATE_FORMAT
The format for displaying the date, according to PHP's date() function.
- TIME_FORMAT
The format for displaying the date, according to PHP's date() function.
- LANGUAGE
The language file (found in the languages sub-directory to use for error and warning messages.
- STRICT_UPDATING
If false, any logged-in user can make changes to a bug. If true, only the reporter, the person to whom the bug is currently assigned, and members of the Manager or Admin group can make changes to a bug.
- PROMOTE_VOTES
The number of votes required to automatically promote a bug from the Unconfirmed to the New status. A value of 0 disables auto-promotion.
- MAX_USER_VOTES
The total number of votes a user may file on bugs. A value of 0 disables the limit.
- RECALL_LOGIN
Whether to show the "Remember Me" checkbox in the login form. When checked, that box will cause a cookie to be set that stores the user's login name or email address and will prefill the login area with that value the next time the user attempts to log in.
- SHOW_PROJECT_SUMMARIES
Whether to show the detailed project stats on the home page.
- FORCE_LOGIN
Whether users must log in before being able to browse the bugs or reports.
