Looks similar to 0008538.

Can you check if setting:

$g_show_assigned_names = OFF;

fixes the problem?

I add the setting

$g_show_assigned_names = OFF;

in the config_inc.php file, but it doesn't fix the problem.

Hi,

I've tested the 1.1.0rc1 and the behaviour is the same as the 1.1.0.

So, this bug seems to have appeared between the 1.1.0a4 and the 1.1.0rc1 versions.

Thanks. that is a really useful info. Now we need to determine exactly at which SVN revision the problem appeared.

Are you able to download the mantis code from SVN?

Yes, no problem, tell me the svn url, and the version(s) to test.

The thing I forgot to indicate, is that I use an old MySQL database (4.0.27) which is not supported yet by Mantis.

So I had the bug 8689 (http://www.mantisbt.org/bugs/view.php?id=8689) but I manage to avoid it with putting in comment the problematic code in core/database_api.php :

#if ( strtolower( $c_charset ) === 'utf-8' ) {

db_query( 'SET NAMES UTF8' );

#}

It perhaps explain the current problem, but it's strange that the bug appears or not depending the user...

I think those are two different issues. And anyway, you will have more errors becasue we are also using nested queries now (also supported starting from MySQL 4.1).

Basically, I'd like you to "svn checkout" the current 1.1 branch from:

https://mantisbt.svn.sourceforge.net/svnroot/mantisbt/branches/BRANCH_1_1_0/mantisbt

then apply the following procedure, starting with v1=4527 (svn revision for a4) and v2=4618 (svn revision for rc1):

Note: to get a given revision use "svn update -r revision"

1. double check the bug is present in v2 but not in v1

2. update code to vtest=(v1+v2)/2 (so the first test is at 4572)

3. test bug
   if present:
   3.a let v2 = vtest
   else
   3.b lst v1 = vtest

4. goto 2

This way, you should be able to quickly isolate the revision where the bug was triggered.

Thanks a lot for your help

OK, I did this kind of dichotomic bugtrack, and the bug appeared between the 4556 and 4557 revisions.

I can try to detect more precisely the bug if I use the same system on files modified between these revisions. But some files seem to have interaction, it can be harder.

The problem seems to come from the "tag" functionality.

If the file bug_view_page.php is in version 4556, it works, in 4557 the bug appears. And the diff for this file is only the add of tag functionality.

For the moment, I cannot be more precise. Hope it helps !

Yes I think it will help :)

Thank you very much for your help so far

I checked the diff and the tag feature contains a lot of queries with subqueries (also known as nested queries). This is a MySQL 4.1 feature and is supposed to break on your installation but I wonder why it does not do that in a graceful way...

Can't you see any error messages in your logs (Apache and/or MySQL)?

I cannot acces now to these logs, the database/web administrators are on holidays. ;) I'll try when they'll come back.

But I think we don't have to worry more about that. It really seems to be a MySQL version bug.

We've planned to upgrade to MySQL 5 in some weeks, I can wait with the alpha4 version for some weeks.

Thanks a lot !

Ok, so let's close this.

Feel free to reopen or create a new one if the problem persist after the upgrade