Mantis Bug Tracker (MantisBT)
Mantis Bug Tracker (MantisBT)
Screenshots
Documentation
For complete documentation, please read the administration guide included with
this release in the doc/<lang>
directory. The guide is available in text, PDF,
and HTML formats.
Requirements
Please refer to section 2.2 in the administration guide for further details.
Installation
mantisbt/config/config_inc.php
if your web server does not have write accessadmin
directory from within the MantisBT installation path. The
scripts within this directory should not be accessible on a live MantisBT
site or on any installation that is accessible via the Internet.UPGRADING
config_inc.php
, custom_strings_inc.php
, custom_relationships_inc.php
,
custom_functions_inc.php
and custom_constants_inc.php
if they existadmin
directory from within the MantisBT installation path. The
scripts within this directory should not be accessible on a live MantisBT
site or on any installation that is accessible via the Internet.CONFIGURATION
This file contains information to help you customize MantisBT. A more detailed doc can be found at https://www.mantisbt.org/docs/
config_defaults_inc.php
config/config_inc.php
config/config_inc.php.sample
for an example.core/*_api.php
- these files contains all the API library functions.
global variables are prefixed by g_
parameters in functions are prefixed with p_
-- parameters shouldn't be modified within the function.
form variables are prefixed with f_
variables that have been cleaned for db insertiong are prefixed with c_
temporary variables are prefixed with t_
.
count variables have the word count
in the variable name
More detail can be seen in the coding guidelines at: https://www.mantisbt.org/guidelines.php
The files are split into three basic categories, viewable pages,
include files and pure scripts. Examining the viewable pages (suffix _page
)
should make the basic file format fairly easy to see. The file names
themselves should make their purpose apparent. The approach used is to break the
work into many small files rather than have a small number of really
large files.
You can set $g_top_include_page
and $g_bottom_include_page
to alter what should be visible at the top and bottom of each page.
All files were edited with TAB SPACES set to 4.
Twice a month we will interview people behind open source businesses. We will talk about how they are building a business on top of open source projects.
We'll never share your email with anyone else.