I have no idea why, but this problem suddenly appeared after I got back
from my xmas holidays... Whenever I perform an action which triggers
some sort of emailing I now get the error message:
PROBLEMS SENDING MAIL TO:
Mailer Error: Language string failed to load: instantiate
from phpmailer. This was when running 0.18.0rc1 and phpMailer 1.71.
There was some mention in the ChangeLog that 0.18.0 final fixed some
problems with phpMailer 1.7x, so I wen ahead and upgraded to mantis
0.18.0, but that only resulted in:
PROBLEMS SENDING MAIL TO:
Mailer Error: Could not load language file
The unit testing script that comes with phpMailer runs without any
failures. I noticed someone had posted a temporary fix for this in the
but that only brought back my first error.
Any ideas on how I can debug this? Why is my language string set to
"instantiate"? I've got the following in my config:
$g_default_language = 'english';
I'm running on a stock (up to date) RedHat 8.0 box.
I have some bugs/requests I would like to report but I am not getting the
email that contains my password when I attempt to sign up at
Here are my issues:
All Projects | View Issues | Print Reports - click any of Icons and notice
the Project is not visible. This makes managing bugs difficult in a bug
triage meeting where it is nice to have printouts of all the new bugs,
without knowing the Project the bug is under.
Jump to a bug - same issue as above, the Project is not there, this makes it
difficult when someone says, "look at bug #3029 - the first thing I need to
know is what Project its in."
Private issue notes have public history - not a big deal but causes social
issues... "what is being hidden from me and why are they talking about
Many users get confused by which project they're in, I don't know how to
make it easier except place the text that says the project beneath menu
"Main | View Issues | Report Issue ...." Instead of at the top. Also if a
user has no default project make sure when they are in Project A then log
out, then log back in that they start out in no Project, instead of Project
They are minor problems but would help so much in overall usability. End
users are funny, small things can hurt first impressions... Mantis is close
to being perfect for my organization though, keep it up, I love it!
From: Christian Hack <christianh@pd...> - 2004-01-14 00:00:53
We do this, but without playing around a bit I can't be sure. I think
this is what you want in your config_inc.php:
# Bug is resolved, ready to be closed or reopened. In some custom
installations a bug
# maybe considered as resolved when it is moved to a custom (FIXED OR
$g_bug_resolved_status_threshold = CLOSED;
> -----Original Message-----
> From: mantisbt-help-admin@...
> [mailto:mantisbt-help-admin@...] On Behalf
> Of Trevor Croft
> Sent: Wednesday, 14 January 2004 9:07 AM
> To: mantisbt-help@...
> Subject: [Mantisbt-help] How To Add a Bugnote to a Resolved bug?
> Is there a config variable to change?
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> Mantisbt-help mailing list
Firstly, I have to say thanks to the Mantis team. Excellent job on a
great system. We have been using it for the Scribus Linux DTP project
(www.scribus.net) for a couple of months now.
Having read the few emails come through on the list re configuration
options, and scanned the documents I have the following question.
Is it possible to tell Mantis to put certain fields on the bug list by
config settings? That is, I would like the version field to be
displayed. Perhaps I have to customise the php/html? Whats the best
place to do so, if so? I would prefer to avoid customisation as much as
possible in terms of the code (as opposed to the config files) as the
spare time I do have goes towards Scribus.