Mantis Bug Tracker - Forums

Upgraded to 1.3.6. Black graphs. No errors in apache log, chrome dev console, nothing. I ran admin/check and nothing there either. I've never used this plugin before so I cannot tell you if it worked for my previous version.

I just upgraded to 1.3.4 (looks nice, btw!).

I use OpenLDAP for authentication, but TLS for encryption. Previously I had to modify the ldap_api.php file to include:

if(ON == config_get( 'ldap_starttls' ) ){
ldap_start_tls($t_ds);
}

And set the value in the config_inc.php file. But it seems ...

After upgrading to the latest (1.2.11) I'm having a lot of permissions issues it seems.

This time the only users that are showing up in the "Assign-to" list for a bug is Administrators, even though Managers and developers are suppose to have access.

I have "Handle an Issue" under Workflow ...

Never mind. I went through each project and added everyone to it. Seems from what I read that this is the only way to give every registered users access to at least see the bugs while not allowing the rest of the known world the ability to see them.

Ok, so I made them private, but now I have to go through every user and/or project and add users to that project in order for them to do anything at all. What in the world happened. Previously public allowed users who were reporters to login and report bugs on that project without being specifically ...

Are your projects set to "public" or "private"?

Thanks atrol. Strangely enough having them set to public, users were still forced to log in on the version I had installed. Must be something that was fixed in this last upgrade. I set them to private and everything is good.

b--

I just upgraded our mantis to 1.2.11 on FreeBSD 7.4-RELEASE-p9 .

Suddenly users can view tickets without logging in. They can't add to or change status, but still, we don't want people able to do this. How do I turn this off?


$g_allow_anonymous_login = OFF;
$g_anonymous_account = '';

is the only ...