Mantis Bug Tracker - Forums

As a general advice. If install.php gives you a blank page (whereas other PHP scripts work fine), try to remove the error suppression operator for the core.php inclusion. This way, critical errors in core.php won't be silently swalloed and instead you should get an indication as to why PHP ...

Not sure whether it helps in your case, but I just hit the same issue on a system where the PHP session module was missing. Does your phpinfo() output include a section for the session module?

Thanks atrol, bug has been filed: http://www.mantisbt.org/bugs/view.php?id=11938

With $g_db_type set to 'mysql', have you tried using 127.0.0.1:3316 instead of localhost:3316?

The mysql libraries treat 'localhost' (seemingly indepent of a given port) as something which should be connected to via the Unix socket living in /var/some/path/mysql.sock per default. Thus, if you are ...

Localhost needs to be the server that holds MySQL :D

Sorry, not true, Mantis runs perfectly fine with a remote MySQL host. The error message points to an authentication problem.

@blackcat: Make sure you can connect from the Mantis host to the MySQL host with the mysql command line utility first ...

Greetings,

just did an upgrade from 1.1.6 to 1.2.1. Following doc/INSTALL, step 3 says

* Point your browser to http://path/to/mantisbt/admin/check.php to ensure that
your webserver is compatible with MantisBT and configured correctly

However, admin/check.php didn't tell me anything about my ...

Hi,

we have a Mantis 1.1.6 installation at opencsw.org with lots of projects (1851 to be precise) and see some heavy performance problems . The view_all_bug_page or my_view_page take about half a minute to load, most of the times they don't even load fully because they hit the maximum execution ...

Hi Jason,

we have a setup with such g_notify_flags running here like a charm. Make sure that you don't have users with global MANAGER privileges (those would receive notificiations for all projects). Assign them global REPORTER (or whatever) privileges and then only grant them MANAGER privileges on ...

Hi all,

we just did an upgrade from Version 0.17.5 to version 1.0.2 this weekend.

Everything is running fine so far, besides a warning message which is displayed to a user each time he changes the status of a bug to resolved (Application warning #403: Database field 'fixed_in_version' not found ...