This is the Mantis system configuration documentation.
Some variables function as toggles (On/Off). Unless otherwise noted 0 is Off and 1 is On.
Email
|
$g_administrator_email
|
This is the email that users should notify when problems occur.
|
$g_webmaster_email
|
This is the webmaster email. Often, this will be the same as the administrator email.
|
$g_from_email
|
This is the email address displayed in the "From: " field.
|
$g_to_email
|
This is the email address displayed in the "To: " field. The email system sends a email to this email address. The actually email to users is sent via the "bcc: " field. This is to help cut down on the number of emails sent per incident. A good use of this would be to use this as a mailing list or archive email address.
|
$g_return_path_email
|
This is the email address that the users can reply to. Usually users should never respond to emails. This may be used by the administrator to track bounced emails and, thus, invalid email accounts.
|
$g_allow_signup
|
This variable toggles whether or not to allow users to signup for their own accounts. Users must enter a valid email address. A randomnly generated password is sent to that address. Users cannot gain access without receiving this email.
If set to off then administrators must create accounts for users. Furthermore they must notify users manually.
|
$g_enable_email_notification
|
Toggle whether the site allows email notification or not.
|
$g_notify_developers_on_new
|
Toggle to notify Developers, Managers, and Administrator when a new bug comes in. Users need to turn on their preference (Email on New) as well.
|
$g_validate_email
|
Toggle to check whether an email is valid before allowing a signup. This checks for a properly formatted email and a valid MX record.
|
$g_check_mx_record
|
Disable the MX record check in the email validation routine.
|
$g_hide_user_email
|
This disables the automatic generation of mailto: links
|
$g_use_x_priority
|
This can disable the generation of the X-Priority header. Apparently Outlook Express treats 0 as high priority.
|
$g_use_bcc
|
Set to 0 as on Windows systems, as long as php-mail-function has its bcc-bug (~PHP 4.0.5/6).
See bug numbers 10136,
11349,
11616,
11797,
|
$g_use_phpMailer
|
Use phpMailer instead of standard mail() function (REQUIRES PHP 4.x.x)
Get the phpMailer-package from http://phpmailer.sourceforge.net
The installation is very simple you only need 2 plain text php-files
- class.smtp.php
- class.phpmailer.php
Copy these files to your php-include-dir (eg: "c:\php\includes" or "/usr/lib/php/includes") and add this path to the "include_path"-entry in the php.ini file.
The installation is described in the readme and there is also a simple example included.
PhpMailer comes with a detailed documentation in phpdoc format. It is distributed under the LGPL.
|
$g_phpMailer_method
|
select the method to mail by:
0 - mail()
1 - sendmail
2 - SMTP
|
$g_smtp_host
|
This option allows you to use a remote SMTP host if you use the phpMailer script in SMTP mode.
|
The email system allows the package to notify users when significant events occur. You should have a working Mail Transport Agent (MTA) on your system. On unix systems this is usually sendmail and usually nothing needs to be done. For problems regarding mail then visit the support forums or read up on the user notes in the mail() function at: http://www.php.net/manual/en/function.mail.php
Users can also signup for their own accounts. Emails must be valid!
You may now use the phpMailer script to send out emails. It is recommended if you currently use Windows and PHP 4.0.4 or higher.
|
Display
|
$g_window_title
|
This is the browser window title (<TITLE> tag).
|
$g_page_title
|
This title is displayed in the viewing area of the HTML page.
|
$g_show_report
|
0 - both
1 - only simple
2 - only advanced
|
$g_show_update
|
0 - both
1 - only simple
2 - only advanced
|
$g_show_view
|
0 - both
1 - only simple
2 - only advanced
|
$g_show_source
|
Create a link at the bottom of each page that displays the source for that page. Only Administrators can view these pages and this should only be used for debug purposes or in a secure environment.
|
$g_show_footer_menu
|
Show the menu at the bottom of the page as well as at the top.
|
$g_show_project_in_title
|
0 : no project name, display $g_page_title
1 : display project name and display $g_page_title
2 : display only project nam, no $g_page_title
|
$g_show_assigned_names
|
When a bug is assigned then replace the word "assigned" with the name of the developer in parenthesis.
|
$g_show_priority_text
|
OFF: Shows priority as icon in view all bugs page
ON: Shows priority as text in view all bugs page
|
$g_show_bug_project_links
|
Show project links when in All Projects mode.
|
Users can set their own default preferences for the show report/update/view preferences but these settings should override those preferences. These settings affect all projects.
|
Default Preferences
|
$g_default_new_account_access_level
|
This is the default access level people are given when their account is created by email. Look in constant_inc.php for other values.
|
$g_default_limit_view
|
Site defaults for viewing preferences.
|
$g_default_show_changed
|
Site defaults for viewing preferences.
|
$g_hide_closed_default
|
Site defaults for viewing preferences.
|
$g_min_refresh_delay
|
Make sure people aren't refreshing too often. If a user tries to set his user preference to be lower then it is bumped back up to this minimum value.
|
$g_default_advanced_report
|
Default advanced report settings.
|
$g_default_advanced_view
|
Default advanced view settings.
|
$g_default_advanced_update
|
Default advanced update settings.
|
$g_default_refresh_delay
|
Default page refresh delay (in minutes). This is for the bug listing pages.
|
$g_default_redirect_delay
|
Default page redirect settings (in seconds).
|
$g_default_email_on_new
|
Default email setting when a new bug is reported.
|
$g_default_email_on_assigned
|
Default email setting when a bug is assigned to a user.
|
$g_default_email_on_feedback
|
Default email setting when a bug is put into feedback status.
|
$g_default_email_on_resolved
|
Default email setting when a bug is resolved.
|
$g_default_email_on_closed
|
Default email setting when a bug is closed.
|
$g_default_email_on_reopened
|
Default email setting when a bug is reopened.
|
$g_default_email_on_bugnote
|
Default email setting when a bugnote is added.
|
$g_default_email_on_status
|
NOT ENABLED
|
$g_default_email_on_priority
|
NOT ENABLED
|
These are the settings that each new account is initialized with.
Default language is set to default site language ($g_default_language).
|
Misc
|
$g_reopen_bug_threshold
|
hr size
|
$g_quick_proceed
|
See fewer confirmation screens between common actions.
|
$g_login_method
|
- PLAIN
- CRYPT
- MD5
- BASIC_AUTH
Some systems (mostly non-unix) do not have crypt support in PHP. MD5 will accomplish almost the same thing. PLAIN is plain text and there is no attempt to secure the password in the database. You will not be able to easily convert between encryption methods so this needs to be chosen at install time. CRYPT was the default until 0.17.0; MD5 is now the default.
|
$g_limit_reporters
|
Limit reporters to only viewing bugs that they report.
|
$g_allow_close_immediately
|
Allow developers and above to close bugs immediately when resolving bugs.
|
$g_allow_account_delete
|
Allow users to delete their own accounts.
|
$g_allow_anonymous_login
|
Allow easy anonymous access.
|
$g_anonymous_account
|
Set the account that users will login as. Make sure this is a viewer or reporter account.
|
$g_cvs_web
|
This allows for quick linking to CVS files via CVSweb or ViewCVS.
|
Access level needed to re-open bugs. Look in the constant_inc.php file if you want to set a different value.
|
Cookies
|
$g_cookie_prefix
|
Set this to a unique identifier. Do not use spaces.
|
$g_string_cookie
|
The name for the users cookie string value.
|
$g_project_cookie
|
The name for the project id cookie.
|
$g_view_all_cookie
|
The name for the view all bugs settings cookie.
|
$g_manage_cookie
|
The name for the manage settings cookie.
|
$g_string_cookie_val
|
The user's cookie_string value. This is a unique identifier for the user.
|
$g_project_cookie_val
|
The user's currently active Project ID.
|
$g_view_all_cookie_val
|
The user's view all bugs settings.
|
$g_manage_cookie_val
|
The users's manage settings cookie.
|
I believe there is a limit of 18 or 20 cookies per domain/directory.
|
Database Tables
|
$g_db_table_prefix
|
Change this is if needed but remember to alter all settings in the db_genrate/upgrade files.
|
$g_mantis_bug_file_table
|
|
$g_mantis_bug_table
|
|
$g_mantis_bug_text_table
|
|
$g_mantis_bugnote_table
|
|
$g_mantis_bugnote_text_table
|
|
$g_mantis_bug_file_table
|
|
$g_mantis_news_table
|
|
$g_mantis_project_category_table
|
|
$g_mantis_project_file_table
|
|
$g_mantis_project_table
|
|
$g_mantis_project_user_list_table
|
|
$g_mantis_project_version_table
|
|
$g_mantis_user_table
|
|
$g_mantis_user_profile_table
|
|
$g_mantis_user_pref_table
|
|
The prefix is used to help make sure table names are unique. This is useful for users who are limited to one database.
|